Outbound Webhooks
Outbound webhooks send a notification to a URL of your choice whenever an endpoint finishes executing. Use them to post to Slack, trigger downstream workflows, or log results to external systems.
Setting up a webhook
Section titled “Setting up a webhook”From wrapd.yaml
Section titled “From wrapd.yaml”Add notify_url and optionally notify_on to an endpoint:
endpoints: - name: deploy method: POST command: ./deploy.sh notify_url: https://hooks.slack.com/services/T.../B.../xxx notify_on: alwaysFrom the dashboard
Section titled “From the dashboard”Open Dashboard → Endpoints, click an endpoint, and set the Notify URL and Notify On fields.
Notify conditions
Section titled “Notify conditions”| Value | Fires when |
|---|---|
always | Every execution (default) |
success | Command exits successfully (exit code 0) |
failure | Command fails (non-zero exit code) |
What’s included
Section titled “What’s included”The webhook POST includes the endpoint name, exit code, status, duration, and command output. If the endpoint is marked as sensitive, the output is omitted.
Pipeline webhooks
Section titled “Pipeline webhooks”Pipelines also support notify_url. The webhook fires once after the entire pipeline run completes — not per step.
Use cases
Section titled “Use cases”- Slack notifications — post deployment results to a channel
- Logging — forward execution results to Datadog, Loki, or a custom log sink
- Chaining — trigger another service after an endpoint completes
- Alerting — use
notify_on: failureto alert only when something breaks