The flow
Starts it 5Logic 6Service 3
The steps in the order they run, from what starts it.
- 1API Recovery WebhookWebhookStarts it
- 2Extract Request ConfigurationSetLogic
- 3Execute Primary API RequestHttp RequestService
- 4Check Primary API SuccessIfLogic
- 5Return Primary API ResponseRespond To WebhookStarts it
- 6Wait Before Retry AttemptWaitLogic
- 7Retry Primary API RequestHttp RequestService
- 8Check Retry API SuccessIfLogic
- 9Return Retry API ResponseRespond To WebhookStarts it
- 10Execute Backup API RequestHttp RequestService
- 11Check Backup API SuccessIfLogic
- 12Return Backup API ResponseRespond To WebhookStarts it
- 13Prepare Failure PayloadSetLogic
- 14Return Final Failure ResponseRespond To WebhookStarts it
How it's built
- Starts on
- Another system calling it
- Steps
- 14, with 3 branches, 1 loop or waits
- Size
- Medium: a working afternoon
- Connects to
- Nothing by connector; it calls services over plain HTTP
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account. You connect your own accounts after importing it; none are included.
What starts it?
It starts on another system calling it.
Does it use AI?
No. Every step is fixed logic or a call to a service, so it does the same thing every time.
How long does it take to set up?
Plan an afternoon. 14 steps is enough that you should read each one before running it.
How do I import it?
Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.
Before you run itNothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 14 steps before you point it at anything that matters.