Back to Catalog

Attach a default error handler to all active workflows

bartvbartv
4625 views
2/3/2026
Official Page

How it works:

Did you ever miss any errors in your workflow executions? I did! And I usually only realised a few days or weeks later. ๐Ÿ™ˆ

This template attaches a default error workflow to all your active workflows. From now on, you'll receive a notification whenever a workflow errors and you'll have peace of mind again.

It runs every night at midnight so you never have to think of this again. Of course, you can also run it manually.

Steps to set up:

  1. Update the Gmail note with your own email address, or replace it with any other notification mechanism. You can also use Slack, Discord, Telegram or text messages..
  2. Activate the workflow.
  3. Relax.

Caveats:

I did not add any rate limiting, so if you have a workflow that runs very frequently and it errors... well let's say your mailbox will not be a nice place anymore.

Ideas for improvement?

If you have any suggestions for improvement, feel free to reach out to me at bart@n8n.io.

Enjoy!

n8n Default Error Handler

This n8n workflow provides a robust, centralized error handling mechanism for your n8n instance. Instead of configuring individual error workflows for each of your active workflows, this single workflow can catch and process errors from all of them.

What it does

This workflow is designed to be set as the default error workflow for your entire n8n instance. When any other workflow on your n8n instance fails, this workflow will be triggered.

  1. Listens for Errors: The workflow starts with an Error Trigger node, which is specifically designed to catch errors from other workflows.
  2. Conditional Email Notification: It includes an If node, which can be configured to send an email notification via Gmail based on specific conditions of the error. This allows for customizable alerting (e.g., only notify for critical errors).
  3. Custom Code Execution: A Code node is included, providing a flexible way to execute custom JavaScript logic. This could be used for advanced logging, data manipulation, or integration with other services not directly supported by n8n nodes.
  4. n8n Workflow Interaction: An n8n node is present, enabling interaction with the n8n instance itself. This could be used to restart failed workflows, update workflow statuses, or trigger other n8n workflows based on the error.
  5. Scheduled Maintenance/Checks (Optional): A Schedule Trigger and Sticky Note are included, hinting at the potential to extend this workflow for scheduled tasks, such as regular checks of workflow statuses or cleanup operations, although they are not connected in the provided JSON.

Prerequisites/Requirements

  • An n8n instance (self-hosted or cloud).
  • A configured Gmail credential (or another email service) if you wish to enable email notifications for errors.
  • Basic understanding of JavaScript for the Code node.
  • An n8n API key/credential if the n8n node is intended to interact with the n8n instance via its API.

Setup/Usage

  1. Import the Workflow: Import this JSON definition into your n8n instance.
  2. Set as Default Error Workflow:
    • Go to your n8n instance settings.
    • Navigate to "Error Workflow" (or similar setting, depending on your n8n version).
    • Select this imported workflow as your default error workflow.
  3. Configure Credentials:
    • If you plan to use the Gmail node for email notifications, configure a Gmail credential.
    • If you plan to use the n8n node to interact with your n8n instance, ensure you have an appropriate n8n API credential set up.
  4. Customize Error Handling Logic:
    • If Node: Modify the conditions in the If node to define when specific actions (like sending an email) should occur based on the error data (e.g., workflow name, error message, error type).
    • Gmail Node: Configure the recipient, subject, and body of the email notification. You can use expressions to dynamically include details from the error trigger.
    • Code Node: Add JavaScript code to perform custom actions upon error, such as logging to an external service, transforming error data, or triggering specific recovery steps.
    • n8n Node: Configure this node to interact with your n8n instance, for example, to restart a specific workflow that failed.
  5. Activate the Workflow: Ensure the workflow is active in your n8n instance.

Now, whenever any workflow on your n8n instance fails, this error handler will be triggered, allowing you to centralize your error monitoring and response.

Related Templates

Auto-create TikTok videos with VEED.io AI avatars, ElevenLabs & GPT-4

๐Ÿ’ฅ Viral TikTok Video Machine: Auto-Create Videos with Your AI Avatar --- ๐ŸŽฏ Who is this for? This workflow is for content creators, marketers, and agencies who want to use Veed.ioโ€™s AI avatar technology to produce short, engaging TikTok videos automatically. Itโ€™s ideal for creators who want to appear on camera without recording themselves, and for teams managing multiple brands who need to generate videos at scale. --- โš™๏ธ What problem this workflow solves Manually creating videos for TikTok can take hours โ€” finding trends, writing scripts, recording, and editing. By combining Veed.io, ElevenLabs, and GPT-4, this workflow transforms a simple Telegram input into a ready-to-post TikTok video featuring your AI avatar powered by Veed.io โ€” speaking naturally with your cloned voice. --- ๐Ÿš€ What this workflow does This automation links Veed.ioโ€™s video-generation API with multiple AI tools: Analyzes TikTok trends via Perplexity AI Writes a 10-second viral script using GPT-4 Generates your voiceover via ElevenLabs Uses Veed.io (Fabric 1.0 via FAL.ai) to animate your avatar and sync the lips to the voice Creates an engaging caption + hashtags for TikTok virality Publishes the video automatically via Blotato TikTok API Logs all results to Google Sheets for tracking --- ๐Ÿงฉ Setup Telegram Bot Create your bot via @BotFather Configure it as the trigger for sending your photo and theme Connect Veed.io Create an account on Veed.io Get your FAL.ai API key (Veed Fabric 1.0 model) Use HTTPS image/audio URLs compatible with Veed Fabric Other APIs Add Perplexity, ElevenLabs, and Blotato TikTok keys Connect your Google Sheet for logging results --- ๐Ÿ› ๏ธ How to customize this workflow Change your Avatar: Upload a new image through Telegram, and Veed.io will generate a new talking version automatically. Modify the Script Style: Adjust the GPT prompt for tone (educational, funny, storytelling). Adjust Voice Tone: Tweak ElevenLabs stability and similarity settings. Expand Platforms: Add Instagram, YouTube Shorts, or X (Twitter) posting nodes. Track Performance: Customize your Google Sheet to measure your most successful Veed.io-based videos. --- ๐Ÿง  Expected Outcome In just a few seconds after sending your photo and theme, this workflow โ€” powered by Veed.io โ€” creates a fully automated TikTok video featuring your AI avatar with natural lip-sync and voice. The result is a continuous stream of viral short videos, made without cameras, editing, or effort. --- โœ… Import the JSON file in n8n, add your API keys (including Veed.io via FAL.ai), and start generating viral TikTok videos starring your AI avatar today! ๐ŸŽฅ Watch This Tutorial --- ๐Ÿ“„ Documentation: Notion Guide Need help customizing? Contact me for consulting and support : Linkedin / Youtube

Dr. FirasBy Dr. Firas
39510

Two-way property repair management system with Google Sheets & Drive

This workflow automates the repair request process between tenants and building managers, keeping all updates organized in a single spreadsheet. It is composed of two coordinated workflows, as two separate triggers are required โ€” one for new repair submissions and another for repair updates. A Unique Unit ID that corresponds to individual units is attributed to each request, and timestamps are used to coordinate repair updates with specific requests. General use cases include: Property managers who manage multiple buildings or units. Building owners looking to centralize tenant repair communication. Automation builders who want to learn multi-trigger workflow design in n8n. --- โš™๏ธ How It Works Workflow 1 โ€“ New Repair Requests Behind the Scenes: A tenant fills out a Google Form (โ€œRepair Request Formโ€), which automatically adds a new row to a linked Google Sheet. Steps: Trigger: Google Sheets rowAdded โ€“ runs when a new form entry appears. Extract & Format: Collects all relevant form data (address, unit, urgency, contacts). Generate Unit ID: Creates a standardized identifier (e.g., BUILDING-UNIT) for tracking. Email Notification: Sends the building manager a formatted email summarizing the repair details and including a link to a Repair Update Form (which activates Workflow 2). --- Workflow 2 โ€“ Repair Updates Behind the Scenes:\ Triggered when the building manager submits a follow-up form (โ€œRepair Update Formโ€). Steps: Lookup by UUID: Uses the Unit ID from Workflow 1 to find the existing row in the Google Sheet. Conditional Logic: If photos are uploaded: Saves each image to a Google Drive folder, renames files consistently, and adds URLs to the sheet. If no photos: Skips the upload step and processes textual updates only. Merge & Update: Combines new data with existing repair info in the same spreadsheet row โ€” enabling a full repair history in one place. --- ๐Ÿงฉ Requirements Google Account (for Forms, Sheets, and Drive) Gmail/email node connected for sending notifications n8n credentials configured for Google API access --- โšก Setup Instructions (see more detail in workflow) Import both workflows into n8n, then copy one into a second workflow. Change manual trigger in workflow 2 to a n8n Form node. Connect Google credentials to all nodes. Update spreadsheet and folder IDs in the corresponding nodes. Customize email text, sender name, and form links for your organization. Test each workflow with a sample repair request and a repair update submission. --- ๐Ÿ› ๏ธ Customization Ideas Add Slack or Telegram notifications for urgent repairs. Auto-create folders per building or unit for photo uploads. Generate monthly repair summaries using Google Sheets triggers. Add an AI node to create summaries/extract relevant repair data from repair request that include long submissions.

Matt@VeraisonLabsBy Matt@VeraisonLabs
208

Automate Dutch Public Procurement Data Collection with TenderNed

TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch ๐Ÿ”— LinkedIn โ€“ Wessel Bulte

Wessel BulteBy Wessel Bulte
247