Start a pipeline run over HTTPS. No API key — the secret token is embedded in the URL. Keep the link private.
Endpoint
POST or GET — /api/webhooks/pipeline/{pipeline_id}/{token}
- Runs synchronously — the HTTP response is returned when the pipeline finishes.
- Optional completion webhook (Settings below) is still POSTed separately when configured.
- In every step,
{{trigger_body}} is the raw POST body string (empty for GET).
Request body (POST, optional)
Send Content-Type: application/json. All fields are optional.
variables — override pipeline task variables for this run (keys you defined under Variables).initial_step_outputs — optional array of strings to seed outputs before step 1 (advanced).skip_steps — optional array of 1-based step indexes and/or step names to skip for this run only (the saved pipeline is unchanged). A skipped step passes its input straight through to the next step, e.g. [2, "Send email"]. Indexes match only the top-level step list; names match at any depth, including inside if/else branches, parallel lanes, and loop bodies.- Caller
variables cannot override trigger_body; it is always set from the raw POST body.
Example curl
Response body (200 OK)
JSON object describing the finished run. ok is false when a step failed or the run was cancelled.
HTTP status codes
| Code | Meaning |
|---|
200 | Run finished (check ok and status in the body). |
403 | Invalid or revoked trigger token. |
404 | Pipeline not found. |
409 | Pipeline is disabled. |
Completion webhook (optional)
If you set a Webhook URL under Settings, the server POSTs a separate JSON payload when the run completes. Optional header X-Pipeline-Signature: sha256=… when a webhook secret is configured.