Start hereAutomationsGuidesYour planThe stackAboutWeekly email▶ YouTubeTelegram

“Her invoice reminders stopped nine days ago. Nobody noticed.”

A Make scenario fails → a row in the error log and a Telegram alert in seconds

By · Updated · Get guides by email

Now a broken automation lasts minutes, not weeks.

Every failing scenario posts to one webhook: the failure is logged in an errors sheet and sent to you on Telegram with the error and the scenario link.

MakeGoogle SheetsTelegram3 operations / run✓ Imported successfully into our Make account

Get the ready-to-import blueprint by email

Yes — email me BuilderStack's weekly issue: one new Make automation or guide a week, from O.S. Maintenance Buildings Ltd (Israel). It may include paid links. Unsubscribe anytime. Optional. We use your address only to send this email; it is stored by Brevo (EU) until you unsubscribe. You can access or delete it at any time — see the privacy policy.

We use your address only to email you this file. Without the box ticked, that is the only email you get, and the address is deleted after 30 days. Privacy policy.

The full build is on this page, free, no email needed.

▶ Watch the 30-second video

Video cover: ERROR ALERT

Short answer

Every failing scenario posts to one webhook: the failure is logged in an errors sheet and sent to you on Telegram with the error and the scenario link.

Tools
Make, Google Sheets, Telegram
Cost to run
3 Make credits (operations) per run

The problem

An automation that breaks quietly is worse than none: the client thinks the reminders go out, and they stopped a week ago. Make emails the owner of the account, which is often not the person who has to fix it, and the email sits between newsletters.

What happens when it runs

  1. In each scenario you care about: an error route with an HTTP module that posts the scenario name, the module, the error message and the scenario link to this webhook
  2. The webhook receives the failure
  3. A new row in the errors sheet: date, scenario, module, error, link, status "new"
  4. A Telegram message to you with the scenario, the error and the link

The tools inside

Disclosure: links marked "paid link" pay us a commission from the vendor if you sign up. Your price is unchanged, and every file here works without them. How we choose tools →

Before you start

Three things to have ready before importing, or Make will ask and you will have to leave halfway:

  • The webhook address (paste it into the HTTP module of each error route)
  • The errors spreadsheet id; columns A–F: date, scenario, module, error, url, status
  • Chat ID

Sheet templates

The file maps columns by position. Start from exactly these headers, in this order — a column in the wrong place writes a phone number into the email column.

  • Errors sheet · date | scenario | module | error | url | status (Sent with the blueprint by email)

How to import (2 minutes)

  1. In Make: Scenarios → Create a new scenario
  2. At the bottom, the three dots (⋯) → Import Blueprint → choose the file you downloaded
  3. Click every module with an exclamation mark: choose your connection (Google, Telegram) — Make creates one in a click if you have none
  4. Replace every value in double curly braces ({{…}}) with your own from the list above
  5. Run once with a test row in the sheet. Only when it passes — Schedule and ON

New to Make? Start here →

No Make account yet?The file imports only into Make. Signing up through the link gives you one month of Core free, and us a commission. The file works without the link.
Sign up for Make →paid link · we earn a commissionPaid link. If you sign up through it we earn a commission from Make; your price is the same, and the link gives you one month of Core free.

The video

Watch on YouTube → · Subscribe to BuilderStack · Telegram channel

Read more

What does not work in it

  • An error route that only sends the alert tells Make the error was handled: Make then skips the error, sends no email, stores nothing and never deactivates the scenario. End the route with Rollback to keep the run marked as failed, or Retry to keep the data as an incomplete execution.
  • It only hears from scenarios whose error route posts to it. A scenario Make deactivated, or one whose trigger stopped firing, sends nothing; keep Make's own error and deactivation emails on for that.
  • Each alert costs one credit in the failing scenario (the HTTP module) and three here. A scenario that fails on every bundle of a big run sends one alert per bundle.

Questions

What does not work in "A Make scenario fails → a row in the error log and a Telegram alert in seconds"?

An error route that only sends the alert tells Make the error was handled: Make then skips the error, sends no email, stores nothing and never deactivates the scenario. End the route with Rollback to keep the run marked as failed, or Retry to keep the data as an incomplete execution. It only hears from scenarios whose error route posts to it. A scenario Make deactivated, or one whose trigger stopped firing, sends nothing; keep Make's own error and deactivation emails on for that. Each alert costs one credit in the failing scenario (the HTTP module) and three here. A scenario that fails on every bundle of a big run sends one alert per bundle.

What do I have to fill in after importing the blueprint?

The webhook address (paste it into the HTTP module of each error route); The errors spreadsheet id; columns A–F: date, scenario, module, error, url, status; Chat ID.

Which tools does it use, and what does a run cost?

Make, Google Sheets, Telegram. Each run uses 3 Make credits (operations).

Is the blueprint free?

Yes. The ready-to-import file is sent free to the email address you enter; the newsletter is a separate box you can leave unticked. The full build is on this page without any email. The file contains no connections and none of our ids, and works whether or not you use the paid Make link on the page.

Build your automation plan →Four questions, three automations ranked for your business.

Paid link. If you sign up through it we earn a commission from Make; your price is the same, and the link gives you one month of Core free.

Next step

All automations →
EMAIL → TASK

Labelled email → task in the log → reminder

Tag an email with one label and it becomes a task with a due date and an alert. One screen for everything that is waiting.

MakeGmailGoogle SheetsTelegram3 ops/run✓ imported in Make
MORNING DIGEST

Every morning: what is due today → one message

At seven in the morning one Telegram message arrives with every task due today, by client. One screen to open the day, instead of five.

MakeGoogle SheetsTelegram3 ops/run✓ imported in Make
OVERDUE ALERT

A task overdue by 3 days → an alert to the consultant, not the client

Overdue tasks do not disappear, they sink. Once a day, every open task 3 days late surfaces in one Telegram message to its owner, before the client asks.

MakeGoogle SheetsTelegram3 ops/run✓ imported in Make

What will it cost? Make cost calculator →Build your automation plan →