Trigger a Spinnaker pipeline execution via webhook
domain: spinnaker.io/docs · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
In the Spinnaker pipeline configuration, add a trigger of type 'Webhook' and note the generated webhook path (typically '/webhooks/webhook/{source}') and optionally a secret
POST to 'https://GATE_HOST/webhooks/webhook/{source}' with Content-Type 'application/json' and any payload; Spinnaker extracts values from the payload using SpEL expressions defined in the trigger config
Alternatively, trigger pipelines directly via the Gate API: POST to '/pipelines/{application}/{pipelineName}' with a JSON body containing 'type: manual' and optional parameter overrides
For the Gate API, authenticate using basic auth, LDAP, OAuth2, or x509 certificates depending on the Spinnaker deployment's authentication configuration
Monitor execution status via GET '/pipelines/{executionId}' on the Gate host, checking 'status' for RUNNING, SUCCEEDED, FAILED_CONTINUE, or TERMINAL
Known gotchas
Webhook triggers require the payload to match any constraints configured on the trigger (e.g. 'payloadConstraints'); a non-matching payload causes the trigger to be silently ignored rather than returning an error
Gate (the Spinnaker API gateway) is not always exposed publicly; in many installations it is internal-only, requiring VPN or service mesh access for API calls
Spinnaker pipeline parameters must be declared in the pipeline configuration before they can be passed at trigger time; runtime parameters not declared in the pipeline are ignored
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?