Skip to main content
Partial today. You can already start a workflow over HTTP via an API trigger. The broader read API — fetching runs and listing workflows — is still in development, and its endpoint shapes and error formats may change.

​
Available today: API triggers

Every deployed workflow can expose a single API trigger — an HTTP endpoint that starts a run:
The cfk_ key is created when you add an API trigger to a workflow. The request body is passed into the run as trigger context, which steps can bind to. See Triggers for the full setup, plus webhook and schedule triggers.

​
In development: the read API

When the read surface ships, you’ll also be able to:
  • Fetch the status and step output of a specific run.
  • List workflows and their recent runs for a team.
These will use the same team-scoped Authorization: Bearer <key> scheme. If you’d like early access, let us know — see Roadmap.

​
See also

  • Triggers — webhook, API, and schedule triggers you can use now.
  • Workflows — the lifecycle the API exposes.
  • Runs & executions — what the run-fetch endpoints will return.