# Push Make Notifications to Slack

**URL:** <https://community.make.com/t/push-make-notifications-to-slack/54513>\
**Category:** Community Archive\
**Created:** [September 10, 2024, 5:39am UTC](https://community.make.com/t/push-make-notifications-to-slack/54513 "2024-09-10T05:39:54Z")\
**Posts on this page:** 5\
**Page:** 1

<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:39am UTC](https://community.make.com/t/push-make-notifications-to-slack/54513/1 "2024-09-10T05:39:54Z")

</div>

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

 ![Screenshot 2024-09-10 at 13.26.38](https://europe1.discourse-cdn.com/flex013/uploads/make/original/3X/2/a/2afc87eef2f167e41ba2cceffb4287b5ebedf9fb.png)

**A walk-through of DR/MNTR/MAKE/Notifications**  
https://www.loom.com/embed/d2389a32d5514ce0a6b56e74978ab8d7

[blueprint.json](https://community.make.com/uploads/short-url/pso858Eb0kk8DaGhy4o6TJi2d4N.json) (156.5 KB)

Upfront, the scenario not highly-efficient, but does stop at two ops when no notifications exists. Further the structuring is helpful for learning a few differing techniques.

---

<div class="post-metadata">

**Author:** ![Mr.Make](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/mr.make/32/93066_2.png) [@Mr.Make](https://community.make.com/u/Mr.Make)\
**Post date:** [September 10, 2024, 6:24pm UTC](https://community.make.com/t/push-make-notifications-to-slack/54513/2 "2024-09-10T18:24:02Z")

</div>

Very nice great work 🙂

---

<div class="post-metadata">

**Author:** ![Lucas\_Ostrowski](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/lucas_ostrowski/32/32163_2.png) [@Lucas\_Ostrowski](https://community.make.com/u/Lucas_Ostrowski)\
**Post date:** [September 14, 2024, 2:18pm UTC](https://community.make.com/t/push-make-notifications-to-slack/54513/3 "2024-09-14T14:18:54Z")

</div>

@ImMichaelCannon, great job!

---

<div class="post-metadata">

**Author:** ![Make\_Bot](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/make_bot/32/14661_2.png) [@Make\_Bot](https://community.make.com/u/Make_Bot)\
**Post date:** [November 20, 2025, 10:20am UTC](https://community.make.com/t/push-make-notifications-to-slack/54513/4 "2025-11-20T10:20:45Z")

</div>



---

<div class="post-metadata">

**Author:** ![Make\_Bot](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/make_bot/32/14661_2.png) [@Make\_Bot](https://community.make.com/u/Make_Bot)\
**Post date:** [November 20, 2025, 10:20am UTC](https://community.make.com/t/push-make-notifications-to-slack/54513/5 "2025-11-20T10:20:47Z")

</div>