Get an alert when a Make scenario fails: what Make already sends, the error route that tells you, and one error inbox for every scenario (free blueprint)

Q: Does Make notify you when a scenario fails?

Yes, by email to the account: immediately on an error, a digest after 5 minutes if more follow, and another email when Make deactivates a scenario. Both are on by default under Email preferences in your profile (Make Help Center, checked 2026-10-12).

Q: Why did Make turn off my scenario?

A scheduled scenario is deactivated after the number of consecutive errors set in Errors before deactivation, 3 by default. A scenario that starts with a webhook is deactivated after its first error. Fix the cause, then switch it back on.

Q: How do I send Make errors to Telegram?

Add an error handler route to the module that fails and put a message module on it, or an HTTP module that posts to one error inbox scenario like the blueprint on this page. End the route with Rollback or Retry so the error is not silently skipped.

Q: Do error handlers use Make credits?

No. Make's pricing FAQ says error handler modules do not use credits (checked 2026-10-12). The modules you add to the route, such as HTTP or Telegram, use one credit each.

Q: What is the difference between Retry and Rollback in Make?

Retry stores the failed run as an incomplete execution so it can be retried, automatically or by hand. Rollback stops the run with an error and keeps nothing to retry.

By Oz Shamo · Updated 2026-10-12 · Get guides by email · YouTube · Telegram

Part of: Make vs Zapier vs n8n for a small business: how each one charges, and when each one wins

Short answer

Make already emails the account owner when a run ends with an error and when it deactivates a scenario (Make Help Center, checked 2026-10-12). For an alert you will actually see, give each scenario an error route that posts the failure to one "error inbox" webhook, which logs it in Google Sheets and sends it to Telegram. End that route with Rollback or Retry, because a route that only alerts makes Make skip the error; each alert costs 4 credits (checked 2026-10-12).

Make emails the account owner when a scenario errors. Check those settings, add an error route, and send every failure to one Google Sheet and Telegram.

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 →

An automation that breaks quietly is worse than none. The client believes the reminders still go out; they stopped nine days ago, when a Google connection expired. This page covers what Make already does when a scenario fails, where that falls short, and a free blueprint that collects every failure in one place.

Make vs Zapier vs n8n for a small businessThe cluster pillar: price per lead, what each one is good at, and when to choose which

What Make already does when a scenario fails

Make's built-in behaviour on errors (Make Help Center: scenario settings, error handling overview, email preferences, incomplete executions; checked 2026-10-12)
Situation	What Make does	Where you see it
A run ends with an error	Emails immediately, then a digest after 5 minutes if more errors follow	The account owner's inbox; the scenario history
Errors in a row on a scheduled scenario	Deactivates it at the "Errors before deactivation" limit, 3 by default	A deactivation email; the scenario is off
An error on a scenario that starts with a webhook	Deactivates it after the first error	The same email
Store incomplete executions is on	Keeps the failed run so it can be retried	The Incomplete executions tab; off by default
A run ends with a warning	Keeps scheduling it	An email only if you switched warning emails on

Error and deactivation emails are on by default; warnings are not. They go to the address on the Make account, which in a consultant's setup is often the client's admin or a shared mailbox, and a digest between newsletters is easy to miss. Two settings are worth checking before you build anything:

Open your Make profile, go to the Email preferences tab, and confirm that error and deactivation emails are on for the organization.
In each scenario that matters, click the gear icon in the scenario editor and turn on Store incomplete executions, so a failed run is kept instead of rolled back.
Leave Errors before deactivation at 3 unless the scenario talks to a service that fails briefly and often; a higher number hides a real outage for longer.

Add an error route that sends the alert

An error route is a second path from a module that runs only when that module fails. Make's own example is a route with a single Slack message on it (Make Help Center, checked 2026-10-12). Instead of a message module in every scenario, send each failure to one small scenario that logs it and alerts you: the error inbox.

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

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.

Blueprint, steps and caveats → · Watch on YouTube

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.

Get all 27 blueprints in one ZIP, by email

Import the error inbox blueprint, open its webhook module, add a webhook and copy the address it shows. Connect Google Sheets and Telegram, and switch it on.
In a scenario you want to watch, right-click the module most likely to fail, usually the Gmail, Google Sheets or HTTP call, and add an error handler route.
On that route add HTTP → Make a request: the webhook address, method POST, body content type application/JSON, body input method Data structure.
Give the data structure four text fields: scenario, module, error, url. Map scenario and url from the Custom and system variables tab (Scenario name, Scenario URL), type the module's name, and map error from the failed module's error message.
End the route with Rollback or Retry (the table below says which).
Break the scenario on purpose, for example with a wrong spreadsheet id, run it once, and check the new row and the Telegram message. Then fix the id.

Use Data structure rather than a typed JSON string: Make escapes quotes and other JSON characters in mapped values automatically there, and an error message almost always contains quotes (apps.make.com/http, checked 2026-10-12). The blueprint escapes the same fields for Telegram with escapeHTML, because one stray "<" in an error message would make Telegram reject the alert.

What the route ends with decides what Make does next

Ending an alert route (Make Help Center, error handlers; checked 2026-10-12)
Route ends with	What Make does next	Use it when
Nothing: only the alert	Skips the error: no error email, nothing stored, the scenario stays on	Never on an alert route
Rollback	Stops the run with an error, as if there were no route, so the email and the deactivation limit still apply	You want Make to stop a broken scenario and the bundle can be redone by hand
Retry	Stores the run as an incomplete execution, for an automatic or manual retry	The data matters, such as a lead or a booking; needs Store incomplete executions

Make's help centre calls these handlers Retry and Skip; its pricing page still uses the older names Break and Ignore (both checked 2026-10-12).

What it costs

Error handler modules use no credits (make.com/pricing FAQ, checked 2026-10-12). Each alert costs 1 credit for the HTTP module in the failing scenario and 3 credits in the error inbox: 40 credits a month at 10 failures, inside the Free plan's 1,000 (checked 2026-10-12). The error inbox is one more active scenario, and the Free plan allows two, so if your other scenarios already fill both slots this one needs Core, $12 a month (checked 2026-10-12).

Check what your scenarios cost togetherPick the automations you run, add the error inbox, see the credits and the plan that fits

Error routes and handlers are in every Make plan, the free one included; this is our link: Sign up (one month of Core free) → 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.

How to import a Make blueprint (and fix the common import errors)Step by step, with the errors people hit on the first import

What does not work

Scenarios that never run. A deactivated scenario, or a trigger that stopped firing, produces no error and so no alert. Make's deactivation email is the backup; keep it on.
One route covers one module. A failure in a module without its own route is handled the default way, so put routes on the modules that call outside services.
Alert floods. A scenario that fails on every bundle of a 200-row run sends 200 alerts and spends 800 credits.
The error inbox can fail too. If its Telegram connection expires, it is a webhook scenario, so Make deactivates it on the first error, and Make's own email is the only warning left.
No link to the failed run. Make's system variables include the scenario URL but no execution URL (Make Help Center, checked 2026-10-12): the alert opens the scenario, and the run is in its History.

Does Make notify you when a scenario fails?

Yes, by email to the account: immediately on an error, a digest after 5 minutes if more follow, and another email when Make deactivates a scenario. Both are on by default under Email preferences in your profile (Make Help Center, checked 2026-10-12).

Why did Make turn off my scenario?

A scheduled scenario is deactivated after the number of consecutive errors set in Errors before deactivation, 3 by default. A scenario that starts with a webhook is deactivated after its first error. Fix the cause, then switch it back on.

How do I send Make errors to Telegram?

Add an error handler route to the module that fails and put a message module on it, or an HTTP module that posts to one error inbox scenario like the blueprint on this page. End the route with Rollback or Retry so the error is not silently skipped.

Do error handlers use Make credits?

No. Make's pricing FAQ says error handler modules do not use credits (checked 2026-10-12). The modules you add to the route, such as HTTP or Telegram, use one credit each.

What is the difference between Retry and Rollback in Make?

Retry stores the failed run as an incomplete execution so it can be retried, automatically or by hand. Rollback stops the run with an error and keeps nothing to retry.

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.