The flow
Starts it 1Logic 14Service 6
The steps in the order they run, from what starts it.
- 1Every day at 09:00CronStarts it
- 2Get last execution timestampFunction ItemService
- 3Get tickets updated after last executionZendeskService
- 4Channel is emailIfLogic
- 5Set search emailSetLogic
- 6Add Pipedrive person Id to Zendesk ticketsMergeLogic
- 7NoOpNo OpLogic
- 8Remove duplicates to make search efficientItem ListsLogic
- 9Pipedrive person Id foundIfLogic
- 10Search persons by emailPipedriveService
- 11Get Zendesk comments for ticketsHttp RequestService
- 12Add comments to ticketsMergeLogic
- 13NoOp1No OpLogic
- 14Rename fields and keep only needed fieldsSetLogic
- 15Process commenst per ticketSplit In BatchesLogic
- 16Split comments to seperate itemsItem ListsLogic
- 17New commentIfLogic
- 18Add comment as a note in PipedrivePipedriveService
- 19NoOp2No OpLogic
- 20Done processingIfLogic
- 21Set new last execution timestampFunction ItemService
How it's built
- Starts on
- A clock
- Steps
- 21, with 4 branches, 1 loop or waits
- Size
- Large: read it before trusting it with anything live
- 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?
Take your time. At 21 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 21 steps before you point it at anything that matters.