The flow
Starts it 6Logic 16Service 4
The steps in the order they run, from what starts it.
- 1Test onceManual triggerStarts it
- 2Call inWebhookStarts it
- 3ConfigSetLogic
- 4Freeze request bodySetLogic
- 5Payload ok?IfLogic
- 6Call 1Http RequestService
- 7Respond invalid payloadRespond To WebhookStarts it
- 8HTTP statusSwitchLogic
- 9Extract call 1SetLogic
- 10Respond budgetRespond To WebhookStarts it
- 11Respond upstreamRespond To WebhookStarts it
- 12Prove retry?IfLogic
- 13Call 2Http RequestService
- 14Skip call 2SetLogic
- 15Call 2 statusSwitchLogic
- 16Carry receiptSetLogic
- 17Extract call 2SetLogic
- 18Has JWS?IfLogic
- 19GET JWKSHttp RequestService
- 20No JWSSetLogic
- 21JWKS ok?IfLogic
- 22GET usageHttp RequestService
- 23Verify Ed25519CodeLogic
- 24JWKS failedSetLogic
- 25Build proofCodeLogic
- 26Respond proofRespond To WebhookStarts it
How it's built
- Starts on
- Another system calling it
- Steps
- 26, with 6 branches
- Size
- Large: read it before trusting it with anything live
- 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?
Take your time. At 26 steps it is large: read it before trusting it with anything live.
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 26 steps before you point it at anything that matters.