The flow
Starts it 1Logic 13Service 8
The steps in the order they run, from what starts it.
- 1Start Calls - 9AM ESTSchedule triggerStarts it
- 2GHL Paginated RequestHttp RequestService
- 3Filter Valid LeadsCodeLogic
- 4Has Leads to Process?IfLogic
- 5Step 1 - Create CustomerHttp RequestService
- 6Step 1.5 - Select Random AgentCodeLogic
- 7Step 2 - Initiate CallHttp RequestService
- 8Loop Setup VariablesSetLogic
- 9Set Attempt Count + Init StatusCodeLogic
- 10Get Call Status from VAPIHttp RequestService
- 11Check Final Status + shouldContinue LogicCodeLogic
- 12Should Continue Loop?IfLogic
- 13Wait Before RetryWaitLogic
- 14Step 3 - Get Call DataHttp RequestService
- 15Prepare Loop PayloadSetLogic
- 16Add Call Status TagHigh LevelService
- 17Step 4 - Set (Parse Call Result)SetLogic
- 18Step 5 - If (Call Answered?)IfLogic
- 19Wait Before Contacts RefreshWaitLogic
- 20Update Contact - Call SummaryHigh LevelService
- 21GHL Paginated UpdatedHttp RequestService
- 22Wait Before RefreshWaitLogic
How it's built
- Starts on
- A clock
- Steps
- 22, with 3 branches, 3 loops or waits
- Size
- Large: read it before trusting it with anything live
- Connects to
- GoHighLevel
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own GoHighLevel 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?
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.
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 22 steps before you point it at anything that matters.