A webhook sends an HTTP request to an external system when an assigned Alert Rule is triggered. Two parts of the webhook let you shape that request — headers and URL parameters — and the status code returned by the external system is your first signal of whether the request succeeded.
This reference describes what each part does. You set headers and URL parameters when you create or edit a webhook.
Headers
Headers are key-value pairs sent with the webhook request. The external system uses them to interpret or authorize the request.
- Each header has a key (the header name) and a value.
- Add a header for anything the receiving system expects, such as a content type or an authorization token.
- For sensitive values such as authorization tokens or API keys, use a secret variable as the value instead of typing the secret directly. See Manage webhook variables.
URL parameters
URL parameters are key-value pairs appended to the webhook's URL as a query string. Use them when the external system reads values from the URL rather than from the request body or headers.
- Each parameter has a key and a value.
- You can use variables in parameter values, the same way you can in headers and the payload.
Status codes
After each request, the external system returns an HTTP status code. Company Settings shows this code in the webhook history log, and it is the quickest way to tell whether a webhook is reaching its endpoint.
| Status code group | Meaning | What it tells you |
|---|---|---|
| 2xx | Success | The external system received the request. |
| 4xx | Client error | The external system rejected the request — often a problem with the URL, headers, parameters, or authorization. |
| 5xx | Server error | The external system received the request but failed to process it on its side. |
A repeated 4xx or 5xx code is a sign the webhook is not being delivered correctly. To investigate, open the history log and review the request and response detail for a failed request.