Flowral computes what's ready, what's blocking what, and when a project actually lands. Two ways to connect: REST and webhooks for software you build, and an MCP connector for the assistants, agent platforms and developer tools your team already uses. Both follow the same permissions.
✦ Included with Pro · No per-call pricing · openapi.json
curl 'https://api.flowral.app/v1/work/available' \
-H 'Authorization: Bearer fl_sk_live_…'
{
"total": 2,
"items": [
{ "taskId": "tsk_3",
"taskName": "Client approval",
"flowName": "Acme: Website relaunch",
"status": "ready",
"criticalPath": true },
{ "taskId": "tsk_9",
"taskName": "Write launch copy",
"flowName": "Acme: Website relaunch",
"status": "ready",
"criticalPath": false }
]
}Same data, same permission model, different consumers. Most teams end up using both.
For code you own: a CI job that opens a flow per release, a CRM that starts the onboarding project when a deal closes, a webhook that tells your system when work becomes ready.
For the assistant your team already talks to. It reads the same flows and can move the work — as the person who connected it, under their role.
| Deciding between them | REST API | MCP connector |
|---|---|---|
| Caller | your software | a person, through an assistant |
| Identity | workspace credential | the signed-in person |
| Auth | API key · client credentials | OAuth 2.1 + PKCE, in a browser |
| Workspace | fixed at issue time | the person's active one, switchable mid-conversation |
| Surface | 51 operations | 49 tools |
| Attribution in the activity feed | the credential's name | the person |
| Stability | versioned contract | tool names are stable; wording isn't |
Including the derived state — status, blockers, critical path, projected finish. You never have to re-implement the dependency rules against raw edges.
Create a project and its whole task graph in one call, with dependencies declared by position. Read, update, archive, restore, schedule, report, export to PDF or PNG, share with a client.
Add, link, estimate, assign, comment, attach. Transitions are endpoints rather than a status field — complete checks the dependencies and the required deliverables, then tells you what it unblocked.
/work/available, /blocked, /in-progress, /overview — across every flow, ranked by what decides the finish date, with the top blockers named.
Critical-path pass with earliest/latest start and slack per task, and the delivery report: completion, effort left, workload per person, what's unestimated.
Members, roles, invitations. List templates and start a flow from one — useful when every engagement of a type should begin identically.
Resolve the name a human typed into an id, across flows, tasks and templates. The call that makes a Slack command feel native.
Created under API & AI in the app, with a role and a set of scopes. It keeps working when the person who made it leaves, and its actions are attributed to it rather than impersonating a colleague.
One header. Right for a script, a cron, a webhook receiver. Shown once at creation and stored hashed — if you lose it, you rotate it.
curl 'https://api.flowral.app/v1/me' \
-H 'Authorization: Bearer fl_sk_live_…'Right for anything long-lived. Tokens expire in an hour, so a leak is worth an hour and rotation is a token request rather than a deploy.
curl -X POST 'https://api.flowral.app/v1/oauth/token' \
-d 'grant_type=client_credentials' \
-d "client_id=$FLOWRAL_ID" \
-d "client_secret=$FLOWRAL_SECRET"
{ "access_token": "fl_at_…", "expires_in": 3600,
"scope": "flows:read flows:write work:write" }The interesting half of a permission model.
viewer and every write is refused, whatever its scopes say. Scopes narrow; they never grant.Scopes: flows:read flows:write work:write
team:read team:write templates:read. Rate limit 120/min per
credential, burst 240, 429 with Retry-After over it.
Connect Flowral to an AI assistant, work platform or developer tool. You will sign in and review access before anything is enabled.
Ask about projects, create tasks and move work forward in conversation.
Bring Flowral projects into the agent platform your organisation manages.
Use Flowral project context while planning, coding and shipping.
Use Flowral tools inside workflows and custom agents.
https://mcp.flowral.app
The connector signs the person in through Flowral's own login — Google, Microsoft, WIINK or a password — and keeps the session it gets back. There is no second account and no key to distribute: revoking the connection ends a session the app already understands. What it may do is a list of scopes shown on the consent screen, and what it can do is whatever that person's role allows, which the API enforces either way.
One thing to weigh with your own head: whatever your assistant asks Flowral for, the company that makes it also holds, under their terms. That's a per-workspace decision, not a switch we should flip for you.
€9 per person per month, everything included — templates, dates, reports, the API, webhooks and the connector. No add-on fee, no per-call pricing, no credits to buy.
Free gives you the whole canvas: unlimited flows, gates, the Ready view, unlimited guests, two people. What Pro adds is everything that involves accounting for the work rather than doing it — a date a client can hold you to, a report an account lead forwards, and programmatic access to the workspace. Metering API calls would make people ration exactly the thing we want in their CI pipeline.
Integration access is included with Pro. Open API & AI in your Flowral workspace and create the API credential, webhook or MCP connection your setup needs.
Use the REST API for software and automated workflows you build. Use the MCP connector when you want Flowral available inside an AI assistant, enterprise agent, developer tool or automation platform.
Use an API key for a simple script or internal automation. Use OAuth client credentials for a long-running service or an integration that needs short-lived access tokens. Both use the same roles and permissions.
A credential belongs to one workspace. Its role sets the maximum access, and its scopes can narrow that access further. It cannot switch workspaces or see projects outside its role.
Yes. Webhooks are included with Pro, so your systems can react when Flowral work changes instead of polling for every update.
The standard limit is 120 requests per minute per credential, with short bursts up to 240. Requests above the limit return 429 with a Retry-After header. Contact us if your integration needs a higher limit.
The REST API, webhooks and MCP connector are included with Pro at €9 per person per month. There is no API add-on, per-call charge or credit system.
The reference is generated from the service, so it can't drift from what ships.
Open the reference