The flow
Starts it 1Logic 7Service 9
The steps in the order they run, from what starts it.
- 1Every 5 minutesCronStarts it
- 2Get agents and adminsZendeskService
- 3Get last execution timestampFunction ItemService
- 4Keep only email and IdSetLogic
- 5Get tickets created after last executionZendeskService
- 6Add Pipedrive agent data to pipedrive contact informationMergeLogic
- 7Add requester information to ticket dataMergeLogic
- 8Get requester informationZendeskService
- 9Add contact owner to ticket dataMergeLogic
- 10Search requester in pipedrivePipedriveService
- 11Keep only needed requester informationSetLogic
- 12Contact exists in PipedriveIfLogic
- 13Get owner information of Pipedrive contactHttp RequestService
- 14Change assignee to Pipedrive contact ownerZendeskService
- 15Add a note requester not foundZendeskService
- 16Keep only requester owner emailSetLogic
- 17Set new last execution timestampFunction ItemService
How it's built
- Starts on
- A clock
- Steps
- 17, with 1 branch
- Size
- Medium: a working afternoon
- Connects to
- Pipedrive, Zendesk
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Pipedrive 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. 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.
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 17 steps before you point it at anything that matters.