- Why a silent failure is the real problem
- Build the error workflow once
- What the alert can include
- When the trigger node itself fails
- Failing on purpose with Stop and Error
- Looking into what went wrong
- A worked example for a lead-sync workflow
- How Zapier and Trello show failures
- My advice for n8n builders
- Frequently asked questions
In n8n, create a separate workflow that starts with the Error Trigger, then open the workflow you want to protect, go to Options, then Settings, and pick it as the Error workflow. It runs whenever an execution fails, so you can send email or Slack alerts. Use the Stop and Error node to fail on purpose.
Why a silent failure is the real problem
An n8n workflow that fails at 3am doesn't tell anyone unless you ask it to. Leads stop syncing, invoices stop sending, and nobody notices until a customer complains. An error workflow lets you control how n8n responds when a workflow execution fails, and the usual answer is simple: tell someone straight away.
Build the error workflow once
- Create a new workflow with the Error Trigger as its first node.
- Name it, for example Error Handler, add a notification step such as email or Slack, and select Save.
- Open the workflow you want to protect, select Options, then Settings.
- In Error workflow, select the workflow you created and select Save.
The error workflow must start with the Error Trigger, and the same one can serve many workflows. So you build one Error Handler and point every important workflow at it.
What the alert can include
| Field | What it tells you | When it's there |
|---|---|---|
| workflow id and name | Which workflow failed | Always |
| error message and stack | What went wrong | Always |
| lastNodeExecuted | Where it stopped | Always |
| mode | How the execution ran | Always |
| execution.id and execution.url | A link to the failed run | Only if saved in the database and the trigger didn't fail |
| execution.retryOf | The run this one retried | Only on retries |
A useful alert message reads something like: workflow name failed at last node executed, with the error message and a link to the execution. That gives whoever picks it up everything they need to start.
When the trigger node itself fails
n8n Docs, in Handle errors gracefully, flag the gap. If the error happens in the main workflow's trigger node, execution.id and execution.url aren't present, because there's no saved execution to point to. The data has less in execution and more in trigger. An alert built only on the execution link will arrive empty, or with a broken link.
So build your message from fields that are always there, such as the workflow name and the error message, and add the execution link only when it exists. An IF node checking whether execution.url is set handles that neatly.
Failing on purpose with Stop and Error
Not every problem throws an error. A workflow can run successfully while doing the wrong thing, such as receiving an empty list of orders on a weekday. The Stop and Error node forces an execution to fail under conditions you choose, and that triggers the error workflow. Put it after an IF node that checks for the bad case, and your Error Handler treats it like any other failure.
Looking into what went wrong
To investigate, review Executions for one workflow or all of them, and load previous execution data into your current workflow to see what each node received. You can also enable Log streaming to investigate errors. Loading a failed execution's data and re-running the broken node is usually the fastest way to find the cause.
A worked example for a lead-sync workflow
Say a workflow copies form leads into your CRM every 15 minutes. Point it at your Error Handler, which posts to a Slack channel with the workflow name, the last node and the error message. Then add an IF node after the CRM step: if the CRM returned no record ID, route to Stop and Error. Now both crashes and quiet failures land in Slack. If you'd rather hand the build to someone, my guide on how to hire a Zapier, Make or n8n expert covers what to ask.
How Zapier and Trello show failures
Zapier's Zap history page logs all Zap runs with their status, showing up to 10 Zap runs per page, and can be filtered by date, Zap name, apps, folder, owner and status. Trello publishes an automation logs and quotas page for its Butler automation. For a wider comparison, see my pieces on n8n and Zapier and n8n alternatives.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
My advice for n8n builders
Build one Error Handler and link every workflow that matters to it. Use fields that are always present in the alert, add Stop and Error for failures that don't throw, and check Executions when an alert arrives. Five minutes of set-up saves a lot of quiet damage.
Want your tool on this list? Featured spots and reviews here are paid partnerships. Here's how to partner with me.
Frequently asked questions
How do I get an alert when an n8n workflow fails?
Build an error workflow that starts with the Error Trigger and sends email or Slack, then select it in the workflow's Settings.
Can one error workflow serve many workflows?
Yes.
How do I make a workflow fail on purpose?
Add the Stop and Error node.
Why is the execution id missing?
It needs the execution saved in the database, and it's absent if the trigger node errored.
How do I see past failures?
Review Executions, or enable Log streaming.
