Route API requests via webhook with retries and backup endpoints

by WeblineIndia ✓ · 30 views · created 2026-06-08 · DevOps

What this workflow does

This workflow has 14 nodes and runs when an HTTP POST request hits its webhook URL. It uses only n8n's built-in nodes.

How it runs

Trigger: When an HTTP POST request hits its webhook URL.

1. Extract Request Configuration (Edit Fields (Set)): sets or maps fields
2. Execute Primary API Request (HTTP Request): calls an HTTP API
3. Check Primary API Success (If): checks a condition and branches into true / false
4. Return Primary API Response (Respond to Webhook): sends the response back to the webhook caller
5. Wait: waits 5 seconds
6. Retry Primary API Request (HTTP Request): calls an HTTP API
7. Check Retry API Success (If): checks a condition and branches into true / false
8. Return Retry API Response (Respond to Webhook): sends the response back to the webhook caller
9. Execute Backup API Request (HTTP Request): calls an HTTP API
10. Check Backup API Success (If): checks a condition and branches into true / false

…plus 3 more steps. See the full node list below.

Before you upgrade to n8n 3.0

Nodes used (6)

• Webhookn8n-nodes-base.webhook
• Edit Fields (Set)n8n-nodes-base.set
• HTTP Requestn8n-nodes-base.httpRequest
• Ifn8n-nodes-base.if
• Respond to Webhookn8n-nodes-base.respondToWebhook
• Waitn8n-nodes-base.wait

From the author

Quick Overview This workflow exposes a webhook that forwards a request to a primary API, retries once after a short delay if it fails, and then fails over to a backup API, returning a structured JSON success or error response to the caller. How it works 1.…

View the original on n8n.io → Check your own copy