# Great Expectations and PagerDuty Alerts | Great Expectations

**URL:** <https://discourse.greatexpectations.io/t/great-expectations-and-pagerduty-alerts-great-expectations/454>\
**Category:** Archive\
**Created:** [October 15, 2020, 2:03pm UTC](https://discourse.greatexpectations.io/t/great-expectations-and-pagerduty-alerts-great-expectations/454 "2020-10-15T14:03:52Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![kyle](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.greatexpectations.io/kyle/32/18_2.png) [@kyle](https://discourse.greatexpectations.io/u/kyle)\
**Post date:** [October 15, 2020, 2:03pm UTC](https://discourse.greatexpectations.io/t/great-expectations-and-pagerduty-alerts-great-expectations/454/1 "2020-10-15T14:03:52Z")

</div>

To be effective, data quality requires a workflow and collaboration. Great Expectations must be able to notify you when validating a batch of data succeeds or fails. Until now the default (and only) notification mechanism was Slack by enabling SlackNotificationAction in their Validation Operators’ configuration.

* * *
This is a companion discussion topic for the original entry at [https://greatexpectations.io/blog/pagerduty-actions/](https://greatexpectations.io/blog/pagerduty-actions/)