Trigger a flow run

Starts a run of a published flow whose first node is a webhook, scheduled, or manual
trigger. A draft flow is rejected with 422 — use actions/test-run to run one.

No Idempotency-Key is required. This is a state transition, not a resource creation.

The response is a snapshot taken at dispatch, so status is always pending and the
timing fields are not yet populated. Read the run back through
GET /cloudflow/v1/flows/{flowId}/runs/{runId} to follow its progress.

A flow holds a concurrency lock while it runs, so triggering one that is already running
returns 409 with the active run embedded in the problem body — no second lookup needed.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required

The ID of the flow to trigger.

Body Params

Optional JSON payload forwarded to the trigger node. Omit or send {} for flows
that need no input.

Headers
string
enum
Defaults to application/json

Generated from available response content types

Allowed:
Responses

Language
Credentials
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json
application/problem+json