canonical: https://jentic.com/apis/xnote.ai/xnote

# XNote API

Workflow automation API for XNote platform providing task, workflow, and integration management. The API exposes 14 endpoints secured with bearer authentication.

## For AI agents

Programmatically create workflow, list workflows. Covers 14 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for productivity only.

## Capabilities

- Create Workflow
- List Workflows
- Get Workflow
- Update Workflow
- Delete Workflow
- Execute Workflow

## Use cases

### Productivity Operations

Use the XNote API to perform productivity operations programmatically. The API provides 14 endpoints covering core functionality including create workflow, list workflows, get workflow.

Example prompt: Call POST /workflows to create workflow

### Automated Executions Management

Automate executions operations by combining multiple XNote API endpoints. Agents can list workflows and then get workflow in a single workflow.

Example prompt: Call GET /workflows to list workflows, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call XNote API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.

Example prompt: Search Jentic for 'create workflow', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/workflows` | Create Workflow |
| GET | `/workflows` | List Workflows |
| GET | `/workflows/{id}` | Get Workflow |
| PUT | `/workflows/{id}` | Update Workflow |
| DELETE | `/workflows/{id}` | Delete Workflow |
| POST | `/workflows/{id}/execute` | Execute Workflow |
| POST | `/tasks` | Create Task |
| GET | `/tasks` | List Tasks |

## Key resources

- **Executions** — Operations related to Executions
- **Integrations** — Operations related to Integrations
- **Tasks** — Operations related to Tasks
- **Workflows** — Operations related to Workflows

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 66 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 82 / 100
  - Developer Experience & Jentic Compatibility: 58 / 100
  - AI-Readiness & Agent Experience: 45 / 100
  - Agent Usability: 94 / 100
  - Security: 75 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/xnote.ai/xnote/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring XNote by hand means implementing its JWT bearer auth against workflow.xnote.ai, tracking token refresh, and handling retries yourself. Through Jentic you install once, import XNote from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** XNote puts the workflow id in the URL path (`/workflows/{id}`), so a rule can pin your agent to one workflow: it can read and execute that workflow and nothing else. You choose the operations it may call, so destructive ones like deleting a workflow are not included unless you add them.
- **Credential handling:** Your XNote token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a workflow' or 'execute a workflow', and Jentic returns the matching XNote operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Asana** — Alternative productivity API
- **Monday** — Alternative productivity API
- **Clickup** — Complementary productivity API

## FAQ

### What authentication does the XNote API use?

The XNote API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I create workflow with the XNote API?

Yes. Use the POST /workflows endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the XNote API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I create workflow through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create workflow'. Jentic returns the matching XNote API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the XNote API have?

The XNote API exposes 14 endpoints covering executions, integrations, tasks operations.

### Can I limit what my agent is allowed to do with the XNote API?

Yes. Because you run Jentic One yourself, your own rules decide which XNote operations and credentials the agent may use. Since XNote puts the workflow id in the URL path (`/workflows/{id}`), you can pin the agent to a single workflow so it only reads and executes that one and nothing else. You also choose which operations it may call, so destructive ones like DELETE `/workflows/{id}` are excluded unless you add them.