Bring ActionFlows into your product
Start ActionFlows and agent conversations from your app, with API keys, the SDK, or hosted MCP.
API
You design ActionFlows and agents in the ActionFlows app. The API is how the rest of your stack starts that work, watches it, and talks to it. Graph editing and Studio config stay in the product. Execution comes to you.
REST, TypeScript SDK, hosted MCP
One organization API key. Three doors. From your backend: list and get ActionFlow and agent metadata, start runs, inspect or cancel them, work the run queue, open agent sessions and stream replies. From Cursor or Claude, the hosted MCP server exposes the same jobs as tools: list_flows, run_flow, run history, queue, start_agent_session, send_agent_message.
When something happens outside, and when you need to know
Inbound ActionFlow webhooks start a run when Stripe, GitHub, or your own service sends a POST. Organization webhooks tell your systems when a run started, succeeded, or failed. Integrations stay on the organization, so every ActionFlow and agent can reuse them.
Frequently asked questions
Start building AI workflows
Create a free account, open a template or a blank canvas, and run your first ActionFlow.
Newsletter
Get product updates
New nodes, agents, and product notes. We send mail only when we have something worth opening.