> For the complete documentation index, see [llms.txt](https://docs.pipekit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pipekit.io/pipekit/pipes/managing-pipes/alerting.md). # Alerting Alert providers are connected at the Organization level. For more information, refer to the [Managing Alert Providers](/pipekit/organization/alert-providers.md) documentation. ## Add Alert Rules 1. Once you have connected an alert provider, click on `Pipes` from the Navbar to navigate to `pipekit.io/pipes` where you'll see a list of pipes. 2. Select the pipe that you want to add alerts for. You'll be redirected to the pipe details page for your selected pipe. 3. Click on the `Alert Rules` tab. You will be prompted to select your alert provider, workflow status such as QUEUED, RUNNING, FAILED, COMPLETED etc and a specific alert message of your choice. ### Alerting specific Slack users For Slack only, you can mention specific Slack users in alerts by referencing them by their Member ID. To find a Slack user's Member ID, navigate to their profile in Slack, click the ellipsis menu, and select "Copy Member ID". Paste this ID into the "CC Users" field in the Pipekit UI when adding your alert rule. You can alert multiple users in the same alert by separating their Member IDs with a comma. ## Validate Workflow Alerts 1. Head to your Slack or MS Teams workspace and find the channel you selected when you connected your alert provider to Pipekit. 2. In that channel, you should see the alert that was added for your selected pipe. 3. Validate the alert by clicking on the link in the alert where you can check the workflow's execution status on the Pipekit UI. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.pipekit.io/pipekit/pipes/managing-pipes/alerting.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.