Bulk trigger workflow executions
Queue several asynchronous executions of one workflow version in a single call
(maximum 10 inputs per request). Each entry in inputs becomes its own execution;
all executions share a single bulk_id for grouped tracking and consolidated
webhook delivery. This route forwards to workflows-engine and requires callers to
pin the workflow version in the path.
The immediate response only confirms the executions were queued. A per-input failure
is reported inline on its executions entry (status: failed + message) — the
bulk call still returns 202 so partial failures don’t lose the queued executions.
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
One input object per execution (1–10), each validated against the workflow version's input schema. Every entry must be a JSON object; a non-object entry (array, string, number) rejects the whole request with 400 rather than failing only that item.
1 - 10 elementsOptional webhook URL applied to every execution in the batch.
"https://your-app.com/webhook"
Optional secret used to sign workflow webhook requests.
"your-secret-key"