The flow
Starts it 1Logic 12Service 4
The steps in the order they run, from what starts it.
- 1When Called by Another WorkflowExecute Workflow triggerStarts it
- 2Resolve Namespace ChainCodeLogic
- 3Get All Mutex RowsData TableService
- 4Plan Namespace ClaimsCodeLogic
- 5Should Wait?IfLogic
- 6Wait For Slot Or QuotaWaitLogic
- 7Split ClaimsSplit OutLogic
- 8Upsert Claimed LevelsData TableService
- 9Limit After UpsertLimitLogic
- 10Verify All Mutex RowsData TableService
- 11Confirm Chain OwnershipCodeLogic
- 12Claim Succeeded?IfLogic
- 13Return TokenSetLogic
- 14Split Rollback KeysSplit OutLogic
- 15Rollback Partial ClaimsData TableService
- 16Limit After RollbackLimitLogic
- 17Wait After RaceWaitLogic
How it's built
- Starts on
- An event in a connected app
- Steps
- 17, with 2 branches, 2 loops or waits
- Size
- Medium: a working afternoon
- Connects to
- n8n data table
- 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 an event in a connected app.
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. 17 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 17 steps before you point it at anything that matters.