> For the complete documentation index, see [llms.txt](https://docs.airops.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.airops.com/your-workspace/monitoring/alerts.md).
# Alerts
Receive alerts through Slack or an incoming webhook when your Workflow fails
Alerts allow you to receive notifications in Slack or through an incoming webhook when your Workflow returns an error.
## How To Create An Alert
To create an alert, follow these steps:
1. Publish your Workflow in order to create an alert
2. Click **Monitor > Alerts**
3. Click **Add Alert**
4. Name your alert
5. Choose the Workflows you want to be notified about
6. Choose how you want to be notified:
* To receive the alert through an incoming Webhook: Click **Add** **Action >** **Webhook** and provide the URL where you will receive a POST request with the data of the error
* To receive the alert through Slack: click on **Add Action > Slack** and select the Slack channel where you want to receive notifications
### Slack Action
When an alert containing a Slack action is triggered, the Slack action sends a message to the selected channel including the Workflow name, error message, and a link to the execution:
### Webhook Action
When an alert containing a Webhook action is triggered, the Webhook action sends a **POST** request to the selected url, with a **JSON** body containing metadata about the errored execution, such as Workflow, Execution id, error message, and more:
```json
{
"status": "error",
"id": 72367362,
"source": "web",
"user_id": 9000,
"airops_app_id": 9999,
"output": null,
"error_code": "SENSITIVE_CONTENT",
"error_message": "Content contains sensitive data"
}
```
---
# 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.airops.com/your-workspace/monitoring/alerts.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.
