Automate Hourly n8n Execution Retries with API Login

What This Workflow Does

This workflow runs every hour. It finds all failed n8n workflow executions. It skips those already retried to avoid duplicates. It logs in using your email and password to get session cookies needed. Then it retries the failed executions in batches of 5. Even if one retry fails, it keeps going. This saves time and lowers mistakes in retrying.

You do not need to check manually for failed runs anymore. Every error is handled automatically.

Tools and Services Used

• n8n Schedule Trigger Node: Starts workflow hourly.
• n8n Set Node: Holds login email, password, instance URL, and execution ID template.
• HTTP Request Node (Login to n8n): Sends POST to /rest/login for session cookies.
• n8n Node (Executions): Queries API for all executions with error status.
• If Node: Checks if failed executions were retried before.
• No Operation Node: Skips executions already retried.
• Split In Batches Node: Divides retry requests into groups of five.
• HTTP Request Node (Retry execution): Sends POST to retry endpoint with session cookie.
• Manual Trigger Node: Lets user run workflow manually for testing.

Inputs, Processing Steps, and Output

Inputs

• n8n account email and password for API login.
• n8n server base URL.
• Workflow executions with error status from n8n API.

Processing Steps

• Trigger fires every hour.
• Login HTTP Request sends credentials and gets session cookie.
• Execution node queries all failed executions with “error” status.
• If node checks if execution has retrySuccessId.
• No Operation node ignores already retried executions.
• Split in Batches node processes executions in batches of 5.
• HTTP Request retry node posts retry calls using session cookie in each batch.
• Workflow loops until all batches retried.

Output

• Failed workflow runs are retried automatically.
• Reduces manual work and chances of missed retries.
• Results in more reliable automation workflows.

Beginner Step-by-Step: How to Use This Workflow in n8n Production

Step 1: Import Workflow

1. Click the Download button on this page to get the workflow file.
2. Open your n8n Editor.
3. Use the Import from File feature to import the downloaded workflow.

Step 2: Configure Credentials

1. Find the Set Node in the workflow.
2. Update username with your n8n email.
3. Update password with your n8n password.
4. Set n8n_instance to your n8n URL (like https://n8n.yourdomain.com/).
5. Check any other IDs, emails or fields that need changing for your setup.

Step 3: Test Workflow

1. Run the Manual Trigger Node to test if login works and retries start.
2. Check for no errors and confirm failed executions are retried.

Step 4: Activate for Production

1. Toggle the activation switch in n8n Editor to turn on the workflow.
2. The workflow will now run once every hour automatically.
3. Monitor first few runs for issues.

Note: If self hosting n8n, consider using self-host n8n services for stable uptime.

Common Setup Problems & Solutions

• 401 Unauthorized: Happens when login credentials are wrong or the login URL is incorrect. Fix the URL so it ends with /rest/login exactly, and check email/password.
• Workflow Not Triggering: Check the Schedule Trigger interval is set to hours and workflow is active.
• No Executions Retried: Verify n8n Node uses filter status = error and the If Node correctly skips those with retrySuccessId.

Customization Ideas

• Add alerts for failed retries by sending Slack or email messages after the retry HTTP Request Node.
• Change Split In Batches Node size for more or fewer retries at once.
• Filter retries for only specific workflows by adding more conditions in the executions query node.
• Use OAuth Credentials for safer login instead of username and password.
• Run the schedule trigger more or less often depending on how fast retries need to happen.

Summary and Results

✓ Saves over one hour daily by automating retries.
✓ Ensures all failed executions retry themselves hourly.
✓ Lowers chance of human error missing failed runs.
✓ Keeps automation workflows running smoother.
✓ Easy to set up and customize for user needs.