n8n Error Workflow: Retry Failed Executions + Gmail Alerts

Automatically retry failed n8n executions and notify you via Gmail

If your n8n workflows occasionally fail due to transient issues like timeouts, rate limits, or temporary server errors, this n8n Error Workflow: Retry Failed Executions + Gmail Alerts helps you “auto-heal” those failures by detecting retryable errors, retrying once through the n8n API, and sending clear Gmail notifications for success or failure.

What this workflow does

• Detects failed executions using the n8n Error Trigger.
• Analyzes the error message and classifies it as retryable (e.g., timeouts, rate limits, and 429/502/503 responses), while also preventing retry loops.
• Waits 30 seconds before attempting recovery.
• Retries the failed execution once via an HTTP request to the n8n REST API (using an n8nApi credential with permission to retry executions).
• Sends Gmail notifications:
  • An “auto-healed” email if the retried execution succeeds.
  • An alert email if the error is not retryable or if the retry attempt fails.

Use cases

• Reduce manual intervention when n8n runs fail intermittently due to rate limits or temporary 5xx responses.
• Monitor production workflows by sending Gmail alerts whenever an execution can’t be recovered.
• Improve reliability for SaaS operators running time-sensitive automations that should recover automatically when possible.

Technical details

• Nodes/tech stack: if, code, wait, gmail, sticky note, http request
• Key integrations: n8n Error Trigger, n8n REST API retry endpoint, Gmail notifications
• Setup highlights:
  • Configure n8nApi credential and your n8n base URL in the retry API request.
  • Provide a Gmail credential and recipient address in both Gmail nodes.
  • Activate the workflow and set it as the Error workflow for workflows you want to monitor.