> For the complete documentation index, see [llms.txt](https://docs.digibee.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digibee.com/documentation/development-cycle/dashboards/alerts/webhook.md).
# How to configure alerts through a webhook
Learn how to configure notification alerts using a webhook.
A webhook can be used to integrate with an existing customer flow. However, it is important to note that the endpoint needed to activate the webhook must be provided by the customer beforehand, as it is not created by the Digibee Integration Platform.
1. At the Platform home page, click on **Monitor**.
2. At the menu on top at the page, click on **Alerts** configuration.
* You can also click on **Settings** and click on **Alerts** at the menu on the left.
3. Click **Create**.
4. Select the pipeline to which you want to assign the alert.
5. Set up the alert according to the metric you want to use.
6. Activate the **Webhook toggle**.
7. Copy the endpoint of your Webhook and place it in the **Webhook URL field**.
After the configuration process is complete, the following JSON output is generated:
```json
{
"realm": "realm",
"environment": "env",
"alertName": "Alert-name",
"pipelineName": "pipeline",
"startsAt": "0001-01-01T00:00:00Z",
"endsAt": "0001-01-01T00:00:00Z",
"status": "firing" // This field can be firing or resolved
}
```
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.digibee.com/documentation/development-cycle/dashboards/alerts/webhook.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
