# Step-by-step guide to send Make errors to slack

**URL:** <https://community.make.com/t/step-by-step-guide-to-send-make-errors-to-slack/53685>\
**Category:** Community Archive\
**Tags:** gmail, slack, error, json, webhooks\
**Created:** [September 1, 2024, 6:39pm UTC](https://community.make.com/t/step-by-step-guide-to-send-make-errors-to-slack/53685 "2024-09-01T18:39:20Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![ImMichaelCannon](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/immichaelcannon/32/48674_2.png) [@ImMichaelCannon](https://community.make.com/u/ImMichaelCannon)\
**Post date:** [September 10, 2024, 5:40am UTC](https://community.make.com/t/step-by-step-guide-to-send-make-errors-to-slack/53685/4 "2024-09-10T05:40:32Z")

</div>

Thanks, @Lucas_Ostrowski, for sharing. You inspired me to share my Make Notification to Slack methodology too.

> [@Push Make Notifications to Slack](https://community.make.com/t/push-make-notifications-to-slack/54513):
>
> A couple weeks back, [Lucas\_Ostrowski](https://community.make.com/u/Lucas_Ostrowski) gracefully shared their [Step-by-step guide to send Make errors to slack](https://community.make.com/t/step-by-step-guide-to-send-make-errors-to-slack/53685). And I can relate because Slack is where my team and are active at, not email. I’d like to share an alternative approach; the scenario checks the Make API for notifications, builds up a message for the scenario creator and updater, and then pushes it to Slack. The blueprint is attached below A walk-through of DR/MNTR/MAKE/Notifications [b…](https://community.make.com/uploads/short-url/pso858Eb0kk8DaGhy4o6TJi2d4N.json)

---

_[View the full topic](https://community.make.com/t/step-by-step-guide-to-send-make-errors-to-slack/53685)._