The flow
Starts it 1Logic 3Service 9
The steps in the order they run, from what starts it.
- 1Every 5 minutesCronStarts it
- 2Get last execution timestampFunction ItemService
- 3Get tickets updated after last executionZendeskService
- 4Get user data of Ticket requesterZendeskService
- 5Add user dataMergeLogic
- 6Only keep needed dataSetLogic
- 7Ticket ExistsIfLogic
- 8Update existing ticketHubspotService
- 9Create or update contactHubspotService
- 10Set new last execution timestampFunction ItemService
- 11Update External Id in Zendesk for contactZendeskService
- 12Create new TicketHubspotService
- 13Update Zendesk ticket with External IdZendeskService
How it's built
- Starts on
- A clock
- Steps
- 13, with 1 branch
- Size
- Medium: a working afternoon
- Connects to
- HubSpot, Zendesk
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own HubSpot and Zendesk accounts. 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. 13 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 13 steps before you point it at anything that matters.