Send Zendesk tickets to Pipedrive contacts and assign tasks
Needs changesNeeds changes. This template uses 2 thing(s) that n8n 3.0 removes: Function Item (legacy), Cron. 2 breaking item(s) found. Static check, last run 2026-10-19.
What to replace before upgrading
| Removed in 3.0 | Replace with |
|---|---|
| Function Item (legacy) Get last execution timestamp, Set new last execution timestamp | Code node, mode 'Run Once for Each Item' |
| Cron Every 5 minutes | Schedule Trigger |
Nodes used (8)
- Function Item
n8n-nodes-base.functionItem - Zendesk
n8n-nodes-base.zendesk - Edit Fields (Set)
n8n-nodes-base.set - Cron
n8n-nodes-base.cron - Merge
n8n-nodes-base.merge - Pipedrive
n8n-nodes-base.pipedrive - HTTP Request
n8n-nodes-base.httpRequest - If
n8n-nodes-base.if
What it does
This workflow automatically sends Zendesk tickets to Pipedrive contacts and makes them task assignees. The automation is triggered every 5 minutes, with Zendesk checking and collecting new tickets which are then individually assigned to a Pipedrive contact. Prerequisites - Pipedrive account and Pipedrive credentials - Zendesk account and Zendesk credentials Note: The Pipedrive and the Zendesk accounts need to be created by the same person / with the same email. How it works 1. Cron node triggers the workflow every 5 minutes. 2. Zendesk node collects all the tickets received after the last execution timestamp. 3. Set node passes only the requesters email and ID further to the Merge node. 4. Merge by key node merges both inputs together, the tickets and their contact emails. 5. Pipedrive node then searches for the requester. 6. HTTP Request node gets owner information of Pipedrive contact. 7. Set nodes keep only the requester owner's email and the agents email and id. 8. Merge by key node merges the information and adds the contact owner to ticket data. 9. Zendesk node changes the assignee to the Pipedrive contact owner or adds a note if the requester is not found. 10. The Function Item node sets the new last execution timestamp.