> For the complete documentation index, see [llms.txt](https://docs.collibra.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.collibra.com/data-quality-self-hosted/admin-configuration/admin-console/alerts/alert-webhook-configuration.md).

# Alert Webhook Configuration

Webhooks allow Data Quality & Observability (self-hosted) to communicate data quality events to a web server in real time. When a data quality event, such as an [alert condition](/data-quality-self-hosted/core-concepts/alerts/working-with-the-alert-builder/adding-dataset-alerts/using-conditions-for-alerts.md) being met, Data Quality & Observability (self-hosted) sends an HTTP POST or PUT request in the form of a JSON payload to the specified URL. The receiving URL, which can be an endpoint in an external collaboration tool, processes the alert based on how you have configured handle such requests outside of Data Quality & Observability (self-hosted).

Webhooks offer the following benefits over SMTP:

* Instantaneous delivery.
* Improves downstream automation.
* JSON format provides dynamic scalability and easier integrations with other systems.

![image of webhooks configuration page in admin console](https://4121921244-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWCrP7Albs8DfJjIQxUxw%2Fuploads%2Fgit-blob-3fbaf0ff314e644e6613e05be86fd7ff1248c830%2Fdq-alerts-webhooks.png?alt=media)

<table><thead><tr><th width="152">Column</th><th>Description</th></tr></thead><tbody><tr><td>Webhook Name</td><td>The name you assign to a webhook to help you identify and use it in Data Quality &#x26; Observability (self-hosted).</td></tr><tr><td>URL</td><td>The location where JSON payloads containing alert information are sent.</td></tr><tr><td>Global Alerts</td><td>When selected, the webhook can send a <a href="/data-quality-self-hosted/core-concepts/alerts/working-with-the-alert-builder/configuring-alert-emails.md">global failure alert</a> when a job fails at runtime.</td></tr><tr><td>Job Creation Alerts</td><td><p>When selected, a webhook alert is triggered when a new dataset is created.</p><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>No new alerts are triggered if the job is edited and re-executed.</p></div></td></tr><tr><td>JSON Template</td><td>The custom JSON template of the webhook.</td></tr><tr><td>Method</td><td><p>The API request method. The options are POST (default) and PUT, which correspond to the following endpoints:</p><ul><li><strong>POST v2/webhook</strong> - The endpoint used to create a webhook.</li><li><strong>PUT v2/webhook</strong> - The endpoint used to edit an existing webhook.</li></ul></td></tr><tr><td>Action</td><td>Click <strong>Actions</strong> to edit or delete a webhook.</td></tr></tbody></table>

## What's next

* [Add a webhook](/data-quality-self-hosted/admin-configuration/admin-console/alerts/alert-webhook-configuration/add-webhooks.md)
* [Working with the Alert Builder](/data-quality-self-hosted/core-concepts/alerts/working-with-the-alert-builder.md)
* [Adding dataset alerts](/data-quality-self-hosted/core-concepts/alerts/working-with-the-alert-builder/adding-dataset-alerts.md)