HumationHuman + Automation
Back to Catalog

Auto-retry engine: error recovery workflow

Francis NjengaFrancis Njenga
1645 views
2/3/2026
ExportPostgreSQLWebhookDatabaseCSV
Official Page

Workflow Documentation: Auto-Retry Engine – Error Recovery Workflow

Detailed Description

The Auto-Retry Engine: Error Recovery Workflow is designed to automate the process of identifying and retrying failed executions in n8n workflows. By leveraging scheduled triggers, API integrations, and conditional logic, this workflow ensures that any failed executions are automatically retried on an hourly basis. This reduces manual intervention, improves system reliability, and ensures smoother workflow operations.

Who is this for?

This workflow is ideal for:

  • Automation Engineers: Managing and maintaining workflows with minimal manual intervention.
  • DevOps Teams: Ensuring high availability and reliability of automated processes.
  • IT Administrators: Reducing downtime and improving system performance by automating error recovery.

What problem does this workflow solve?

  • Manual Error Handling: Eliminates the need for manual monitoring and retrying of failed executions.
  • Improved Reliability: Automatically retries failed executions, reducing downtime and improving workflow success rates.
  • Time Efficiency: Saves time by automating repetitive error recovery tasks, allowing teams to focus on higher-priority work.

What this workflow does

This workflow automates the following steps:

  1. Scheduled Monitoring: Checks for failed executions hourly using a schedule trigger.
  2. Error Filtering: Identifies executions that have failed and filters out those that have already been successfully retried.
  3. Authentication: Logs into the n8n instance using API credentials to retrieve session details.
  4. Automatic Retry: Retries the failed executions using the n8n API.
  5. Batch Processing: Processes multiple failed executions in batches to avoid overloading the system.

Setup

Prerequisites

To use this workflow, you’ll need:

  • n8n Account: To create and run the workflow.
  • n8n API Credentials: For logging into the n8n instance and retrying executions.
  • HTTP Request Node: Configured to interact with the n8n API.
  • Schedule Trigger: Set to run the workflow hourly.

Setup Process

  1. Configure Schedule Trigger

    • Set the trigger to run hourly to check for failed executions.

  2. Set Login Credentials

    • Add your n8n instance URL, username, and password in the Set Node.

  3. Integrate n8n API

    • Use the HTTP Request node to log into the n8n instance and retrieve session details.

  4. Retry Failed Executions

    • Configure the HTTP Request node to retry failed executions using the session details.

  5. Batch Processing

    • Use the Split in Batches node to process multiple failed executions in batches.

How to customize this workflow

Tailor the workflow to fit your specific needs:

  • Adjust Schedule Frequency

    • Modify the schedule trigger to run at different intervals (e.g., every 30 minutes).

  • Add Notifications

    • Integrate email or Slack notifications to alert teams about failed retries.

  • Refine Error Filtering

    • Customize the filtering logic to exclude specific types of failed executions.

  • Scale Batch Size

    • Adjust the batch size in the Split in Batches node to optimize performance.

Conclusion

The Auto-Retry Engine: Error Recovery Workflow is a powerful tool for automating error recovery in n8n workflows. By reducing manual intervention and ensuring failed executions are retried automatically, this workflow enhances system reliability and operational efficiency. Whether you're managing a few workflows or a complex automation ecosystem, this workflow ensures your processes run smoothly and consistently.

n8n Auto-Retry Engine Error Recovery Workflow

This n8n workflow provides a basic framework for handling errors in other n8n workflows by attempting to re-execute them. It's designed to be a foundational component for building more robust error recovery mechanisms within your n8n automation ecosystem.

What it does

This workflow outlines a conceptual process for retrying failed n8n workflow executions. While the provided JSON is a minimal template, it demonstrates the core components needed for such a system:

  1. Triggering the recovery: It can be manually initiated or run on a schedule.
  2. Identifying failed workflows: (Conceptual, would require external input or a more complex trigger).
  3. Preparing for retry: Edits fields, potentially extracting necessary data for the retry.
  4. Looping for retries: Processes multiple failed items or attempts multiple retries.
  5. Attempting re-execution: Calls another n8n workflow (the one that failed).
  6. Conditional logic: Checks the outcome of the re-execution.
  7. Handling success/failure: Placeholder for actions after a retry attempt.

Prerequisites/Requirements

  • n8n Instance: You need a running n8n instance to import and execute this workflow.
  • n8n API Key (for the n8n node): If you intend for the "n8n" node to trigger other workflows via the n8n API, you will need to configure an n8n API key credential.

Setup/Usage

  1. Import the workflow:
    • Copy the provided JSON code.
    • In your n8n instance, go to "Workflows" and click "New".
    • Click the "Import from JSON" button (usually a cloud icon with an arrow pointing down).
    • Paste the JSON and click "Import".
  2. Configure Trigger:
    • Decide whether you want to trigger this workflow manually (using the "Manual Trigger" node) or on a schedule (using the "Schedule Trigger" node). You can delete the one you don't need.
    • If using "Schedule Trigger", configure the desired interval (e.g., every 5 minutes, once a day).
  3. Configure "Edit Fields" (Set) Node:
    • This node is a placeholder. You would typically use it to extract relevant data from the error context (e.g., the original input that caused the failure in another workflow) and prepare it for the retry.
    • Modify the fields to set the data required by the workflow you intend to retry.
  4. Configure "Loop Over Items" (Split in Batches) Node:
    • This node allows you to process multiple failed items or attempt retries in batches. Adjust the batch size as needed.
  5. Configure "n8n" Node:
    • This node is crucial for triggering the actual workflow you want to retry.
    • Select the "Execute Workflow" operation.
    • Choose the n8n credential (if using API key for execution).
    • Specify the ID or name of the n8n workflow you want to retry.
    • Pass the data prepared in the "Edit Fields" node as input to the target workflow.
  6. Configure "If" Node:
    • This node provides conditional logic based on the outcome of the "n8n" node's execution (the retry attempt).
    • You would typically check for success or failure status from the n8n node's output.
    • The "True" and "False" branches are placeholders for subsequent actions (e.g., logging success, sending alerts for persistent failures, moving to a dead-letter queue).
  7. Activate the Workflow:
    • Once configured, activate the workflow by toggling the "Active" switch in the top right corner of the n8n editor.

Related Templates

Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax

Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions

Daniel NkenchoBy Daniel Nkencho
601

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

Auto-reply & create Linear tickets from Gmail with GPT-5, gotoHuman & human review

This workflow automatically classifies every new email from your linked mailbox, drafts a personalized reply, and creates Linear tickets for bugs or feature requests. It uses a human-in-the-loop with gotoHuman and continuously improves itself by learning from approved examples. How it works The workflow triggers on every new email from your linked mailbox. Self-learning Email Classifier: an AI model categorizes the email into defined categories (e.g., Bug Report, Feature Request, Sales Opportunity, etc.). It fetches previously approved classification examples from gotoHuman to refine decisions. Self-learning Email Writer: the AI drafts a reply to the email. It learns over time by using previously approved replies from gotoHuman, with per-classification context to tailor tone and style (e.g., different style for sales vs. bug reports). Human Review in gotoHuman: review the classification and the drafted reply. Drafts can be edited or retried. Approved values are used to train the self-learning agents. Send approved Reply: the approved response is sent as a reply to the email thread. Create ticket: if the classification is Bug or Feature Request, a ticket is created by another AI agent in Linear. Human Review in gotoHuman: How to set up Most importantly, install the gotoHuman node before importing this template! (Just add the node to a blank canvas before importing) Set up credentials for gotoHuman, OpenAI, your email provider (e.g. Gmail), and Linear. In gotoHuman, select and create the pre-built review template "Support email agent" or import the ID: 6fzuCJlFYJtlu9mGYcVT. Select this template in the gotoHuman node. In the "gotoHuman: Fetch approved examples" http nodes you need to add your formId. It is the ID of the review template that you just created/imported in gotoHuman. Requirements gotoHuman (human supervision, memory for self-learning) OpenAI (classification, drafting) Gmail or your preferred email provider (for email trigger+replies) Linear (ticketing) How to customize Expand or refine the categories used by the classifier. Update the prompt to reflect your own taxonomy. Filter fetched training data from gotoHuman by reviewer so the writer adapts to their personalized tone and preferences. Add more context to the AI email writer (calendar events, FAQs, product docs) to improve reply quality.

gotoHumanBy gotoHuman
353