Keep sales teams in the loop by sending new Zendesk email ticket comments into Pipedrive as notes on the right person. Good for companies that want customer context in the CRM without manual copy and paste.

A daily schedule runs at 09:00 and reads the last time it ran. It pulls Zendesk tickets updated since that time and keeps only email channel tickets. The workflow builds a unique list of sender emails, searches Pipedrive for matching people, and attaches the person Id to each ticket. It then fetches the ticket comments, splits them into single items, and keeps only comments created after the last run. Each new comment is posted as a formatted note in Pipedrive. Batch and dedup steps help reduce API calls and keep things efficient.

You need active Zendesk and Pipedrive accounts and credentials in n8n. Set an initial last run date so the first sync only brings what you expect. Expect less manual work, fewer copy errors, and better handoffs from support to sales. Helpful for sales reps, account managers, and RevOps teams that want support insight inside the CRM.

• Daily schedule at 09:00 pulls only recent Zendesk updates using a stored last run time.
• Email channel filter ensures only email conversations are synced to the CRM.
• Unique email list creation reduces duplicate Pipedrive searches and API calls.
• Pipedrive person lookup by email maps the correct person Id to each ticket.
• Comment fetch per ticket with an HTTP request joins comments to ticket data.
• Comment splitting and date filter send only new comments since the last run.
• Notes posted to Pipedrive include sender name and message content for clear context.
• Batch processing manages load and helps stay within API limits.

• Reduce manual logging from 30 minutes to 5 minutes per rep per day
• Automate up to 90% of support to CRM note entry
• Improve note accuracy by removing copy and paste errors
• Connect Zendesk and Pipedrive so sales sees full context
• Scale to handle growing ticket volume without extra admin work

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You'll need accounts with Zendesk and Pipedrive. See the Tools Required section above for links to create accounts with these services.
3. In n8n Cloud, open Credentials. Create a Zendesk credential: double click the Zendesk nodes, choose Create new credential, then follow the on screen steps. If needed, generate an API token in your Zendesk Admin center under API settings.
4. Create a Pipedrive credential: double click the Pipedrive nodes, choose Create new credential, then follow the on screen steps. If using an API token, get it from your Pipedrive personal settings under API.
5. Open the Cron node and confirm the time is set to 09:00 in your local time zone. Adjust if your team needs a different schedule.
6. Open the Get tickets updated after last execution node and keep the query updated>{{ $json["lastExecution"] }} so only recent tickets are pulled.
7. Open the Get last execution timestamp function. Add a fallback ISO date for first run, such as seven days ago, so you control how much history is imported.
8. Review the Set search email and Channel is email nodes. Leave them as is unless your Zendesk uses a different email field or channels you want to include.
9. For a safe test, disable the Cron node and click Execute workflow. Create or update an email ticket in Zendesk and check the execution. Confirm the Add comment as a note in Pipedrive node shows success.
10. Open the matched person in Pipedrive and verify the new note appears. If no note is created, confirm the Zendesk sender email matches a Pipedrive person primary email.
11. If you hit rate limits or large volumes, adjust the Split in Batches size and consider spreading runs or lowering frequency.