The flow
Starts it 5Logic 3Service 2
The steps in the order they run, from what starts it.
- 1WebhookWebhookStarts it
- 2Payment Token ConfigsCodeLogic
- 3Validate & Verify X-Payment HeaderCodeLogic
- 4Verify PaymentOne ShotService
- 5Response: Missing or Invalid Payment Headers1Respond To WebhookStarts it
- 6On Successful Payment SimulationIfLogic
- 7Settle PaymentOne Shot SynchService
- 8Response: Payment InvalidRespond To WebhookStarts it
- 9Response: 200 - Payment SuccessfulRespond To WebhookStarts it
- 10Response: Payment FailedRespond To WebhookStarts it
How it's built
- Starts on
- Another system calling it
- Steps
- 10, with 1 branch
- 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. 10 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.
Nothing 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 10 steps before you point it at anything that matters.