Webhooks
Observability and issue webhook sources that can start workbench jobs
Webhook sources deliver events into Plural from systems outside the workbench. A source is either an observability webhook (alerting systems such as Datadog, Grafana, or PagerDuty) or an issue webhook (an issue tracker or a source-control provider).
Creating the source produces a Plural webhook URL. Authenticate that URL the way the provider requires; each provider page below describes its own secret or handshake. The source does not, by itself, start a job. To run a workbench when a payload matches, add a trigger on the workbench. See Webhook triggers.
Observability webhook sources are also documented under Observability Webhooks.
Capabilities
- Observability — receive alert payloads from an external monitoring system. Sources: AlertOps, Datadog monitor notifications, Grafana contact points, New Relic workflows, PagerDuty V3 incident events, and Sentry issue alerts from an internal integration. Plural's own monitor alerts are raised internally and need no webhook; see Plural.
- Issue — receive issue events from a tracker (Asana, Azure DevOps, Jira, Linear, ServiceNow), or pull-request events from a source-control provider (Bitbucket Cloud, Bitbucket Data Center, GitHub, GitLab).
Setup
Each provider page above walks through creating the source in Console, registering the URL and secret in the provider, and troubleshooting failed deliveries. Console also shows an inline setup guide while you create a webhook source.
Related
- Integrations — how tools, webhooks, and chatbots differ
- Automating workbench jobs — match a payload and start a job