canonical: https://jentic.com/apis/flowdash.com/flowdash

# Flowdash API

Jentic publishes the only available OpenAPI specification for Flowdash API, keeping it validated and agent-ready. Flowdash is a workflow management platform used by operations teams to build internal tools without code. The API exposes endpoints for listing workflows, creating and updating tasks, querying active tasks, and reading or writing custom field values on those tasks. All requests authenticate with a bearer token issued from the Flowdash dashboard.

## For AI agents

Create and update operational tasks inside Flowdash workflows, list active work, and write custom field values for ops automation.

## Scope

Does not handle chat, email, or document storage - use for Flowdash workflow and task operations only.

## Capabilities

- List all workflows configured in a Flowdash workspace
- Create tasks against a specific workflow with starting field values
- Retrieve only active (non-completed) tasks for a workflow
- Update an individual task by its unique identifier
- Read and write custom field values on a workflow's task schema
- Filter tasks by workflow ID for routing to the right ops team
- Trigger downstream automations by advancing tasks through workflow stages

## Use cases

### Ops Triage Queue

Push events from external systems into Flowdash as tasks so an operations team can triage them in one place. Use POST `/workflows/{workflowId}/tasks` to create the task with the right field values, and GET `/workflows/{workflowId}/tasks/active` to drive a live work queue. This replaces ad hoc spreadsheets with a structured ops backlog in under a day of integration work.

Example prompt: Create a task in workflow 'fraud-review' with fields {customer_id: '12345', risk_score: 87} via POST `/workflows/{workflowId}/tasks.`

### Task Resolution Automation

Update tasks through PATCH `/workflows/{workflowId}/tasks/{uniqueId}` as upstream signals arrive - for example, marking a task complete when a payment clears. Combine with GET on the same path to fetch task state before deciding next steps. Each update is keyed off the workflow ID and the task's unique identifier.

Example prompt: Look up task 'task_7f2' in workflow 'wf_kyc' and update its status field to 'approved' once verification has passed.

### Workflow Schema Discovery

Read the field definitions on a workflow via GET `/workflows/{workflowId}/fields` before pushing data, so your agent never sends payloads that fail validation. Useful for adaptive integrations that connect new Flowdash workflows without hardcoding field names. The endpoint returns the field IDs, types, and constraints for the workflow.

Example prompt: Call GET `/workflows/{workflowId}/fields` for workflow 'onboarding-v2' and return a list of field names and types.

### AI Agent Ops Integration via Jentic

Agents use Jentic's intent search to find Flowdash operations, load the input schema for task creation, and execute calls under a scoped credential. This pattern lets a support agent open Flowdash tasks directly from a conversation without the operator wiring a custom backend. Jentic keeps the bearer token isolated.

Example prompt: Use Jentic to search 'create a Flowdash task', load the POST `/workflows/{workflowId}/tasks` schema, and create a task with the values provided by the user.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/workflows` | List all workflows in the workspace |
| POST | `/workflows/{workflowId}/tasks` | Create a task in a workflow |
| GET | `/workflows/{workflowId}/tasks/active` | List active (non-completed) tasks |
| GET | `/workflows/{workflowId}/tasks/{uniqueId}` | Retrieve a task by unique ID |
| PATCH | `/workflows/{workflowId}/tasks/{uniqueId}` | Update fields on a task |
| GET | `/workflows/{workflowId}/fields` | List field definitions for a workflow |

## Key resources

- **Workflows** — List configured workflows in the Flowdash workspace.
- **Tasks** — Create, retrieve, and update tasks scoped to a workflow.
- **Active Tasks** — Filter to non-completed tasks for live work queues.
- **Fields** — Read the field schema attached to each workflow.

## Why Jentic

- **Setup:** Wiring the Flowdash API by hand means managing its bearer token, threading the workflowId through the task URL on every call, and building your own retry and error handling. Through Jentic you install once, import Flowdash from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Flowdash puts the workflow id in the URL path (`/workflows/{workflowId}/tasks/...`), so a rule can pin your agent to one workflow: it can read and create tasks for that workflow and nothing else. You choose the operations it may call, so a task update via PATCH is not included unless you add it.
- **Credential handling:** Your Flowdash bearer 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 Flowdash task', and Jentic returns the POST `/workflows/{workflowId}/tasks` operation with its field schema so the agent supplies the right values without browsing the reference docs.

## Related APIs

- **Asana API** — General-purpose work and task management with broader collaboration features than Flowdash.
- **ClickUp API** — Task and document platform that overlaps with Flowdash for ops use cases.
- **Slack API** — Notify channels when Flowdash tasks change state.

## FAQ

### Why is there no official OpenAPI spec for Flowdash API?

Flowdash does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Flowdash API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Flowdash API use?

The Flowdash API uses HTTP bearer token authentication. Generate a token in the Flowdash dashboard and pass it as Authorization: Bearer <token>. Jentic stores it encrypted in your Jentic One instance.

### Can I create tasks programmatically with the Flowdash API?

Yes, POST `/workflows/{workflowId}/tasks` creates a task in a workflow with the field values you supply. Read the field schema first via GET `/workflows/{workflowId}/fields` to ensure the payload matches the workflow definition.

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

The OpenAPI spec does not declare explicit rate limits. Treat the API as conservatively rate-limited for high-frequency agent traffic and back off on 429 responses returned by the service.

### How do I list only active tasks in a workflow through Jentic?

Search Jentic for 'list active Flowdash tasks', load the GET `/workflows/{workflowId}/tasks/active` schema, and execute with the workflow ID. The endpoint excludes completed tasks so you only see live work.

### Can the Flowdash API update fields on existing tasks?

Yes, send a request to `/workflows/{workflowId}/tasks/{uniqueId}` with the changed field values. The task is keyed by its unique ID, which is returned when the task is created.

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

Yes. Because Jentic One is self-hosted, you set the rules that decide which Flowdash operations and credentials your agent may use. Since Flowdash puts the workflow id in the URL path (`/workflows/{workflowId}/tasks/...`), you can pin the agent to a single workflow so it only lists and creates tasks there and touches nothing else. You also choose the exact operations it may call, so a task update via PATCH `/workflows/{workflowId}/tasks/{uniqueId}` is excluded unless you explicitly allow it.