The flow
Starts it 1Logic 10Service 5
The steps in the order they run, from what starts it.
- 1When Scheduled Time ReachedSchedule triggerStarts it
- 2Calculate Dynamic Last Run TimeCodeLogic
- 3Fetch SF MQL LeadsSalesforceService
- 4Loop Over Lead BatchesSplit In BatchesLogic
- 5Commit Last Run Time UpdateCodeLogic
- 6If Email ExistsIfLogic
- 7Extract Domain from EmailCodeLogic
- 8Update Lead Missing EmailSalesforceService
- 9Wait 2 SecondsWaitLogic
- 10Fetch Journey Data from APIHttp RequestService
- 11Tidy API Response DataCodeLogic
- 12Locate Email in DataCodeLogic
- 13If Valid Email FoundIfLogic
- 14Wait 1 Second for UpdateWaitLogic
- 15Update Lead No Journey EmailSalesforceService
- 16Update Lead with DataSalesforceService
How it's built
- Starts on
- A clock
- Steps
- 16, with 2 branches, 3 loops or waits
- Size
- Medium: a working afternoon
- Connects to
- Salesforce
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Salesforce account. You connect your own accounts after importing it; none are included.
What starts it?
It starts on a clock.
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. 16 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 16 steps before you point it at anything that matters.