Trigger workflow execution
Start an asynchronous workflow execution through api-service. This route forwards to workflows-engine and requires callers to pin the workflow version in the path.
The immediate response only confirms the workflow was queued. Downstream workflow
lifecycle statuses are running, completed, failed, and cancelled.
To queue several executions of the same version in one call, use the bulk trigger route.
Authorizations
API key passed as an Authorization Bearer token: Authorization: Bearer YOUR_API_KEY
Path Parameters
Workflow ID or slug to execute.
Workflow version ID to execute.
Query Parameters
Optional compatibility query parameter for execution completion webhooks. The request body field takes precedence when both are present.
Body
Input values defined by the workflow version. May be omitted for workflows with no inputs.
Optional webhook URL for workflow execution completion.
"https://your-app.com/webhook"
Optional secret used to sign workflow webhook requests.
"your-secret-key"