Handle API retries with exponential backoff, jitter, Slack and email alerts

Reusable Retry Handler with Exponential Backoff, Jitter, Slack/Email Alerts, and Manual Suspend

How it works

This workflow is a reusable retry and resilience pattern for n8n.

It can be called from any workflow using the Execute Workflow node. It runs a transient operation, classifies the result, retries retryable failures using exponential backoff with jitter, and stops retrying after a configurable maximum number of attempts.

At a high level, it:

• Accepts a generic operation input from another workflow • Runs an HTTP/API operation that can be replaced with any app node • Retries only transient failures such as 408, 409, 425, 429, 500, 502, 503, and 504 • Avoids retrying common permanent errors such as 400, 401, 403, 404, and 422 • Calculates exponential backoff delay with random jitter to reduce retry storms • Sends a Slack message when all retries are completed • Sends an email notification when all retries are completed • Suspends the workflow at a Wait node for manual review • Optionally continues to Stop and Error so your global Error Workflow can capture the final failure

This template is useful for production workflows that call third-party APIs, SaaS apps, databases, or internal services that may fail temporarily.

Set up steps