# Step-by-step guide to send Make errors to slack **URL:** \ **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:** 6\ **Page:** 1
**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 1, 2024, 6:39pm UTC](https://community.make.com/t/step-by-step-guide-to-send-make-errors-to-slack/53685/1 "2024-09-01T18:39:20Z")
Hello, Makers! For many years, I used to get notifications about errors, warnings, and any malfunction on production directly from Slack. Since I started using Make, this has been my biggest issue, as I don’t monitor my email constantly but instead check it twice a day. It wasn’t a big issue when I was using Make for myself. However, since I manage a portfolio of customers, I decided to build a system that forwards notifications directly to Slack. I described the final workflow in my article: [How to Get Make Error Notifications from Slack](https://lostrowski.pl/how-to-get-make-error-notifications-from-slack). ![hPhybRLtWdaYlaFGNqv3OPwL5A](https://europe1.discourse-cdn.com/flex013/uploads/make/original/3X/8/4/84ffe1c9b44bb5675a62568518daafdce3f02f90.webp) What’s your way to monitor errors? ---
**Author:** ![samliew](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/samliew/32/13327_2.png) [@samliew](https://community.make.com/u/samliew)\ **Post date:** [September 2, 2024, 2:55am UTC](https://community.make.com/t/step-by-step-guide-to-send-make-errors-to-slack/53685/2 "2024-09-02T02:55:16Z")
> [@Lucas\_Ostrowski](#): > > I described the final workflow in my article You can combine the OpenAI and Parse JSON into a single “Transform text to structured data” module, or use the free Groq “Create a JSON chat completion” module, that outputs **data as a collection** without needing to use another “Parse JSON” module. This saves an operation, and if you use Groq it’s a free alternative to OpenAI. ### Example Here is a [Groq](https://www.make.com/en/integrations/groq) example on how to specify the variables that you want to match from the text content. This setup is also similar to what you’d do with the OpenAI Structured Data module. ![](https://europe1.discourse-cdn.com/flex013/uploads/make/original/3X/d/2/d2cdb9054e0784482d05f2f7241c47257e77686e.png) ### Output ![](https://europe1.discourse-cdn.com/flex013/uploads/make/original/3X/9/e/9e7e66588cb9b23edabfc05a2e0dffb4b499d8fd.png) (Google’s [about page](https://about.google/) didn’t contain any Google email or phone numbers, so it was left empty) Hope this helps! — @samliew ---
**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 2, 2024, 6:13am UTC](https://community.make.com/t/step-by-step-guide-to-send-make-errors-to-slack/53685/3 "2024-09-02T06:13:14Z")
@samliew Nice! I didn’t know about this one. Thank you. ---
**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")
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) ---
**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:23am UTC](https://community.make.com/t/step-by-step-guide-to-send-make-errors-to-slack/53685/5 "2025-11-20T10:23:00Z")
This topic was automatically closed because it's resolved or inactive. Please, start a new topic. ---
**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:23am UTC](https://community.make.com/t/step-by-step-guide-to-send-make-errors-to-slack/53685/6 "2025-11-20T10:23:03Z")
Archived on November 20, 2025, 10:23am UTC