Sync Zendesk Ticket Comments to Pipedrive Notes - n8n Workflow

Sales Operations and Revenue Teams needing unified customer data.
Customer Success Managers who use Zendesk for support but Pipedrive for relationship management.
System Administrators looking for robust n8n templates for CRM integration.
Anyone needing an automated solution to prevent data silos between helpdesk and CRM systems.

Maintaining consistency between helpdesk tools like Zendesk and CRM platforms like Pipedrive is crucial for high-performing teams. This sophisticated n8n workflow solves the problem of disconnected communication logs. It operates automatically using a Cron n8n trigger, ensuring that every time a customer sends an update to an existing Zendesk ticket via email, that information is seamlessly transferred to the appropriate contact's record in Pipedrive as a linked note. By leveraging several key n8n node types, this automation efficiently filters for recent updates, searches Pipedrive contacts by email, and only synchronizes truly new comments, saving API usage and ensuring high data integrity. This specific n8n template is essential for creating a 360-degree view of the customer journey directly within the CRM.

This n8n workflow is scheduled to run once daily, focusing on incremental updates to maintain efficiency.

1. Trigger and Timestamp Retrieval: The n8n trigger, a Cron node, starts the process daily at 09:00. Immediately after, a Function n8n node retrieves the timestamp of the last successful execution stored in the workflow's static data.


2. Fetch Zendesk Tickets: The Zendesk n8n node queries for all tickets that have been updated since the retrieved timestamp.


3. Filtering by Channel: An If n8n node filters these results, continuing the flow only if the ticket was received via the 'email' channel.


4. Pipedrive Contact Matching: The workflow extracts the sender's email address, removes duplicate email entries via an Item Lists n8n node, and uses the Pipedrive n8n node to search for a corresponding 'Person' contact.


5. Data Preparation and Merge: If a match is found, the Pipedrive Person ID is merged back into the original Zendesk ticket data item.


6. Comment Synchronization: For each matched ticket, an HTTP Request n8n node fetches all associated comments from Zendesk. The subsequent Item Lists n8n node splits the comment array into individual items.


7. New Comment Check: A critical If n8n node compares the comment creation date against the lastExecution timestamp. Only comments created after the previous run are considered new.


8. Create Pipedrive Note: The Pipedrive n8n node (acting as the final action n8n node) creates a new 'Note' in Pipedrive. The note content includes the Zendesk message body and is explicitly linked to the matched Pipedrive Person ID.


9. Complete and Update: After processing all comments via a batch loop, a final Function n8n node updates the static data with the current execution time, setting the reference point for the next run of this reliable n8n workflow.

1. Import: Copy the provided n8n workflow JSON and import it into your n8n instance.


2. Credentials: You will need to set up two main credentials:

1. Review Configuration: Check the Zendesk n8n node to ensure the 'query' is correctly formatted if your timezone requires adjustments.


2. Activation: Activate the n8n workflow. The Cron n8n trigger is set to run daily at 09:00 UTC by default.

This automation utilizes several specialized n8n node types:

Every day at 09:00 (Cron n8n trigger):
Function: Trigger the n8n workflow daily on a set schedule.
Key Configuration: Set to run at 9 AM.

Get tickets updated after last execution (Zendesk n8n node):
Function: Retrieves only those Zendesk tickets that have been updated since the time recorded in the previous execution.
Key Configuration: Operation getAll, Query updated>{{ $json["lastExecution"] }}.

Search persons by email (Pipedrive n8n node):
Function: Finds the corresponding Pipedrive contact using the email address extracted from the Zendesk ticket's sender information.
Key Configuration: Resource person, Operation search, Term sourced from SearchEmail field.

Add comment as a note in Pipedrive (Pipedrive n8n node):
Function: Creates the note in Pipedrive, ensuring synchronization of the communication.
Key Configuration: Resource note, Content template pulls sender details and comment body. Links to person_id retrieved earlier in the n8n workflow.

Get last execution timestamp / Set new last execution timestamp (Function n8n node):
Function: Uses getWorkflowStaticData to persist the time of the previous run and update it upon completion, which is vital for effective incremental syncing. This is a common pattern in advanced n8n templates.
* Key Configuration: Custom JavaScript code for data persistence.