The flow
Starts it 6Logic 6Service 10
The steps in the order they run, from what starts it.
- 1Receive LeadWebhookStarts it
- 2Cleanup ScheduleSchedule triggerStarts it
- 3Validate and NormalizeCodeLogic
- 4Prepare Cleanup TableData TableService
- 5Input Valid?IfLogic
- 6Find Expired KeysData TableService
- 7Hash Normalized PayloadCryptoService
- 8Reject Invalid RequestRespond To WebhookStarts it
- 9Delete Expired KeyData TableService
- 10Create or Reuse Lead TableData TableService
- 11Create or Reuse Key TableData TableService
- 12Find Active KeyData TableService
- 13Classify ReplayCodeLogic
- 14Replay Conflict?IfLogic
- 15Reject Replay ConflictRespond To WebhookStarts it
- 16Already Exists?IfLogic
- 17Return Existing LeadRespond To WebhookStarts it
- 18Find Possible DuplicateData TableService
- 19Classify Possible DuplicateCodeLogic
- 20Insert New LeadData TableService
- 21Store Idempotency KeyData TableService
- 22Return New LeadRespond To WebhookStarts it
How it's built
- Starts on
- Another system calling it
- Steps
- 22, with 3 branches
- Size
- Large: read it before trusting it with anything live
- 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 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 22 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.
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 22 steps before you point it at anything that matters.