Silent failures are the biggest risk once automations run unattended. This is a reusable error workflow: point any of your workflows at it, and whenever one of them fails you get an email with everything needed to fix it. The Error Trigger node starts this workflow…
Written and tested by AltFTool
When a workflow fails
Starts the workflow when the Error event occurs.
Format error details
Runs custom JavaScript to transform or manipulate the data flowing through the workflow.
Send alert email
Handles the Email Send step in this workflow.
Silent failures are the biggest risk once automations run unattended. This is a reusable error workflow: point any of your workflows at it, and whenever one of them fails you get an email with everything needed to fix it.
The Error Trigger node starts this workflow automatically when a linked workflow fails. A Code node reads the details n8n passes along and builds a clear subject such as [Workflow error] Nightly order sync failed at "Get orders", plus a plain-text and HTML body with the workflow name and ID, the failing node, the error message, the run mode, the time, a link to the saved execution and the stack trace. It also handles the case where a trigger fails before any execution starts.
The email is sent through any SMTP server: your own mail provider, a transactional service, or a workspace account.
FAQ
Copy the workflow JSON from this page, open the n8n editor, click on an empty canvas and paste with Ctrl+V (Cmd+V on macOS). You can also download the .json file and choose Import from File in the workflow menu. Save the workflow, then attach credentials before activating it.
It uses Error Trigger, Code and Email Send. Any node that connects to an external service needs your own credential — open each node after import and select or create one. Trigger, logic and transformation nodes usually need no credentials.
The workflow format is the same on both. If a node appears as unknown or outdated after import, update n8n to a recent version or, on self-hosted instances, install the required community node package. Features such as $env access are available on self-hosted instances only.
Start by changing the trigger (schedule, webhook or app event) and the destination nodes to match your stack — it is listed under Engineering, DevOps. Edit prompts, field mappings and filters in the relevant nodes, use expressions like {{ $json.field }} to map data, and test with a manual execution before activating.
A lightweight uptime checker you can run on your own n8n instance. Every five minutes it requests each URL on your list and decides whether the site is healthy. The HTTP Request node is set to…
Keep track of new versions of the tools you depend on without watching every repository by hand. Every six hours this workflow asks the public GitHub API for the latest release of each repository on…
This workflow turns n8n into a small, well-behaved JSON API. A Webhook node listens for POST requests on the path contact-intake and hands the response over to Respond to Webhook nodes, so you…
Messy spreadsheets are one of the most common reasons people start automating. This workflow shows a complete cleanup pipeline using only built-in nodes, and it ships with a deliberately untidy…
This workflow is an interactive, hands-on tutorial designed to teach you the absolute basics of JSON (JavaScript Object Notation) and, more importantly, how to use it within n8n. It's perfect for…
by Lucas PeyrinThis template is an interactive, step-by-step tutorial designed to teach you the most important skill in n8n: using expressions to access and manipulate data. If you know what JSON is but aren't…
by Lucas Peyrinn8n is a trademark of n8n GmbH. AltFTool is not affiliated with, endorsed by or sponsored by n8n. Community templates are credited to their creators and link to the original listing; AltFTool originals are written and tested by the AltFTool team.