Automate Zendesk Ticket Assignment with n8n and Pipedrive

What This Automation Does

This workflow connects Zendesk and Pipedrive to assign tickets automatically.
It helps support staff by finding who asked for help and giving their tickets to the right sales agents.
The workflow runs every 5 minutes to check for new tickets and does the assignments by itself.
You save time and avoid mistakes because tickets go straight to correct owners.

Tools and Services Used

• Zendesk: Stores and manages customer support tickets.


• Pipedrive: CRM with contacts and sales owners.


• n8n Automation Platform: Runs the workflow to move data and update tickets.

How This Workflow Works (Inputs → Processing → Output)

Inputs

• New Zendesk tickets created since last check.


• Requester info (email) from Zendesk users.


• Contacts data from Pipedrive searched by requester emails.


• List of Zendesk agents and admins.

Processing Steps

• Gets last run time to know when to check tickets.


• Fetches tickets created after last run time.


• Finds requesters’ emails from ticket data.


• Searches Pipedrive for matching contacts by email.


• Gets owner info of found Pipedrive contacts.


• Finds Zendesk agents with emails matching Pipedrive owners.


• Checks if requester is found in Pipedrive.


• If yes, assigns Zendesk ticket to matching Pipedrive contact owner.


• If no, adds an internal note to Zendesk ticket about missing contact.


• Updates last execution time for next run.

Output

• Zendesk tickets assigned correctly to Pipedrive sales owners.


• Internal notes added to tickets with requester missing in Pipedrive.


• Workflow ready to run repeatedly every 5 minutes and stay updated.

Who Should Use This Workflow

The workflow is for support managers who get many Zendesk tickets daily.
You want to stop wasting hours looking up who requested support and assigning tickets by hand.
You need a way to make sure tickets go fast to the right sales agents in Pipedrive based on requester info.
This works well if Zendesk and Pipedrive are actively used and connected through API keys in n8n.

Beginner Step-by-Step: How to Use This Workflow in n8n

1. Download and Import Workflow

1. Click the Download button on this page to save the workflow file.
   
2. Open your n8n editor where you build workflows.
   
3. Use the Import from File option in n8n and choose the downloaded file.
   

2. Configure Credentials

1. Add your Zendesk API credentials in n8n credentials manager.
   
2. Do the same for your Pipedrive API credentials.
   

3. Update Any IDs or Emails

1. Check if node settings use any specific IDs for users, channels, or tickets and update them if needed.
   
2. Make sure the query expressions match field names in your Zendesk and Pipedrive accounts.
   

4. Understand and Paste Code

1. Locate the Get last execution timestamp node.
   
2. Verify the JavaScript code is the same as below to track last workflow run:
   

   // Get or set the last execution time
   const staticData = getWorkflowStaticData('global');
   if(!staticData.lastExecution){
     staticData.lastExecution = new Date().getTime();
   }
   item.executionTimeStamp = new Date().getTime();
   item.lastExecution = staticData.lastExecution;
   return item;
   

   
   

5. Test the Workflow

1. Manually trigger the workflow to check for errors.
   
2. Look if tickets get assigned correctly or notes are added.
   

6. Activate the Workflow

1. Turn on the Cron node to run the workflow every 5 minutes.
   
2. Monitor workflow executions in n8n for any problems.
   

That’s all you need to run this automation in production.
For self-host n8n users, consider performance and API rate limits.
self-host n8n setup can help with stability.

Customization Ideas

• Change Cron node interval to run less or more often depending on ticket volume.
  
• Add filters in Zendesk query for tickets, such as only open or high priority tickets.
  
• Log emails of requesters not found in Pipedrive to a spreadsheet or database.
  
• Send email notifications to Pipedrive owners when they get new ticket assignments.
  
• Use other CRM nodes (Salesforce, HubSpot) for contacts lookup instead of Pipedrive.
  

Troubleshooting

• Zendesk API returns no tickets: Check the last execution time is set right and matches Zendesk’s time zone.
  
• Pipedrive search returns no results: Verify requester email format. Emails must match exactly or use fuzzy search if possible.
  
• Ticket assignment fails with authorization errors: Make sure Zendesk API keys have permissions to update tickets and are correct in n8n.
  

Pre-Production Checklist

• Confirm API credentials in n8n for Zendesk and Pipedrive are valid.
  
• Test the workflow manually with new tickets after setting up.
  
• Check the lastExecution timestamp initializes and updates correctly.
  
• Make sure requester emails are fetched and matched properly.
  
• Watch if Zendesk tickets get assigned correctly in test runs.
  

Deployment Guide

Turn on the Cron node to start automatic execution.
Watch the workflow run in n8n UI for errors or success.
Add alerts or email notifications for failures if possible.
For self hosting n8n, monitor server load and API rate limits carefully.
See self-host n8n for hosting options.

Summary

✓ Automatically connect Zendesk tickets with correct Pipedrive owners.
✓ Save hours of manual work checking and assigning tickets.
✓ Improve customer support speed and accuracy.
✓ Easily test and activate in n8n with clear credential setup.
✓ Flexible to customize and extend by adding filters or notifications.