Webhooks let Watchplane notify external systems in real time when something happens — a monitor goes down, an incident is created, or an anomaly is detected. If a tool accepts HTTP requests, you can connect it via a webhook.
When to use webhooks
- Custom alerting — route alerts into an internal system your team already uses
- Incident management — auto-create tickets in PagerDuty, Opsgenie, Jira, or Linear when a monitor fails
- Automation — trigger runbooks, scaling actions, or notifications through Zapier or Make
- Audit trails — log every Watchplane event to your own database or data warehouse
For Slack specifically, use the native Slack integration — it’s simpler and supports interactive buttons.
Setting up a webhook
Go to Settings → Webhooks → Add webhook and enter:
Name — a label for your own reference (e.g. “PagerDuty alerts”).
URL — the endpoint that will receive the events. Must be publicly accessible.
Events — choose which events trigger a delivery:
| Event | When it fires |
|---|---|
| Monitor down | A check fails |
| Monitor up | A monitor recovers |
| Incident created | An incident is opened |
| Incident acknowledged | Someone acknowledges an incident |
| Incident resolved | An incident is closed |
| Anomaly detected | The ML service detects unusual response times |
You can subscribe to all events or only the ones you care about.
Testing your webhook
After saving, click Send test event. Watchplane sends a sample payload to your URL so you can verify it’s receiving events before anything goes wrong in production.
Delivery and retries
Watchplane expects a 2xx response from your endpoint. If it doesn’t receive one, it retries up to 3 times with exponential backoff. You can see the full delivery history for each webhook — including the response code and body — from the webhook detail page.
Payload format
Every event includes a common structure with the event name, timestamp, and the affected resource. The full payload schema for each event is documented in the API Reference.
Developers: Webhooks can also be managed via the API and CLI. See the API Reference for the complete payload schemas and the CLI commands for scripting.