Elementary supports sending alerts to several destinations beyond Slack and Microsoft Teams, including PagerDuty, Opsgenie, Jira, Linear, and generic webhooks. You can configure alert distribution rules to route alerts to these different channels and tools, allowing for flexible alerting setups based on tags, model names, owners, or criticality. This enables you to send alerts to the most relevant recipients or systems for each type of failure or warning [Alerts and Incidents Overview](https://docs.elementary-data.com/features/alerts-and-incidents/alerts-and-incidents-overview). However, sending the same alert to multiple destinations (e.g., both Slack and email for the same model failure) is not natively supported as a single action. The current alert routing system evaluates rules in order and sends the alert to the first matching destination only. This means you cannot, out-of-the-box, send a single alert to multiple integrations simultaneously for the same event [Alert Rules](https://docs.elementary-data.com/features/alerts-and-incidents/alert-rules). Email alerting is a frequently requested feature, but as of now, it is not supported. There are open feature requests for email and other integrations, and workarounds (such as querying the Elementary schema and building your own notification pipeline) have been discussed, but these require custom development and do not offer the same state management and formatting as native integrations [Support email alerts integration](https://github.com/elementary-data/elementary/issues/855), [Slack Q&A: email alerts](https://slack.com/archives/C02CTC89LAX/p1683597421726199). Elementary is open to contributions for new integrations, and there is a plugin-like approach for adding new messaging integrations, as seen in community discussions about Google Chat and other channels. If you have development resources, you can contribute or build your own integration following their guidelines [Send alerts to Google Chat](https://github.com/elementary-data/elementary/issues/1789). In summary: - Multiple alert destinations for the same event are not natively supported. - Several integrations exist (Slack, Teams, PagerDuty, Opsgenie, Jira, Linear, webhooks). - Email is not yet supported. - You can contribute new integrations or use webhooks for custom solutions. - For now, you may need to implement a workaround if you require multi-destination alerting for the same event.

Webhooks are not currently available as an official integration in Elementary OSS. The knowledge sources indicate that while Slack and Microsoft Teams integrations are supported in OSS, there is no mention of a generic webhook integration for OSS. In fact, a Slack discussion explicitly states that there is not a generic webhook notification available in OSS at this time, though it is recognized as a requested feature by the community. Workarounds, such as connecting other tools via Slack alerts and third-party services like Zapier, have been suggested, but native webhook support is not present in OSS as of now [Slack forum: webhook option](https://slack.com/archives/C02CTC89LAX/p1663302266708379). Webhooks are available as a beta feature in the Elementary Cloud Platform, but you need to reach out to enable it for your instance [Webhooks (Beta) in Cloud](https://docs.elementary-data.com/cloud/integrations/alerts/webhooks). If you need webhook support in OSS, you may consider following or contributing to related feature requests in the Elementary GitHub repository.