🔓 Unlock all 10,000+ workflows & prompts free Join Newsletter →
✅ Full access unlocked — explore all 10,000 AI workflow and prompt templates Browse Templates →
Home › n8n › Workflow
January 22, 2026

Zendesk + Pipedrive: ticket notes synced to CRM

Zendesk + Pipedrive: ticket notes synced to CRM - n8n workflow automation template
Lisa Granqvist Partner Workflow Automation Expert
Zendesk + Pipedrive: ticket notes synced to CRM - n8n workflow automation template
Get a free AI assessment → Get a free AI assessment → ⬇️ Use template

Your support team has the real customer story, but it gets trapped inside Zendesk. Sales is left guessing, chasing updates in Slack, or asking for “quick context” right before a follow-up call.

This Zendesk Pipedrive sync is a lifesaver for sales managers who hate surprises, support leads who don’t have time to re-explain tickets, and ops folks trying to keep handoffs clean. The outcome is simple: ticket comments show up as readable notes in Pipedrive, automatically.

You’ll learn what the workflow does, what you need to run it, and how to avoid the common “it ran but nothing happened” headaches.

How This Automation Works

Here’s the complete workflow you’ll be setting up:

n8n Workflow Template: Zendesk + Pipedrive: ticket notes synced to CRM

Why This Matters: Sales Follow-Ups Lose Context Fast

When a customer has an open issue, the details change daily. A new comment arrives. The priority shifts. Someone on the support team finds the actual root cause, but sales never sees it unless a human remembers to pass it along. That’s how you end up with awkward follow-ups (“Just checking in…”) right after the customer wrote a frustrated update in Zendesk. It’s not just time wasted. It’s lost trust, messy internal handoffs, and deals that stall because the owner doesn’t have the full picture.

It adds up fast. Here’s where it breaks down in the real world.

  • Support updates live in Zendesk, but sales works out of Pipedrive, so information stays split across tools.
  • Copy-pasting ticket comments into CRM notes is boring work, which means it often doesn’t happen.
  • Follow-ups get delayed because reps need to ask someone for context before writing a useful email.
  • When the wrong person owns the relationship, ticket updates don’t reach the right rep at all.

What You’ll Build: Daily Zendesk Notes Logged in Pipedrive

This workflow runs on a daily schedule and looks for Zendesk tickets that were updated since the last time it ran. It filters those tickets so you’re only processing the ones coming through the email channel (which usually maps best to identifiable customers). Then it pulls the relevant email address from each ticket, de-duplicates the list so you don’t run the same search over and over, and finds the matching person in Pipedrive by email. Once the person match is confirmed, the workflow fetches the Zendesk ticket comments and writes them into Pipedrive as clean notes tied to the right contact. Finally, it stores a “last execution timestamp” so tomorrow’s run only grabs what changed.

The workflow starts at 09:00, checks what’s new in Zendesk, and matches tickets to people in Pipedrive using email. After that, it retrieves comments and creates Pipedrive notes in batches, so it can handle multiple updated tickets without choking.

What You’re Building

Expected Results

Say you have 20 tickets updated in a day and sales wants visibility on each one. Manually, even a quick routine (open ticket, copy the latest comment, find the contact in Pipedrive, paste as a note) is maybe 3 minutes per ticket, which is about 1 hour of tedious work. With this workflow, the daily trigger runs on its own at 09:00 and processes updates in batches. Your “time spent” becomes a quick spot-check, usually just a few minutes.

Before You Start

  • n8n instance (try n8n Cloud free)
  • Self-hosting option if you prefer (Hostinger works well)
  • Zendesk for pulling updated tickets and comments.
  • Pipedrive to find people and write notes.
  • Zendesk + Pipedrive API credentials (create in each tool’s admin settings).

Skill level: Intermediate. You’ll connect accounts, confirm fields like email, and test a run with real data.

Want someone to build this for you? Talk to an automation expert (free 15-minute consultation).

Step by Step

Daily 09:00 check-in. A Cron trigger starts the automation every morning. Before pulling tickets, it loads the timestamp from the prior run so you only process what’s new.

Pull updated Zendesk tickets and filter them. Zendesk provides the list of tickets updated after that saved timestamp. The workflow checks the ticket channel and continues only when the ticket is email-based, which keeps the match logic more reliable.

Match tickets to the right Pipedrive person. It extracts email, removes duplicates, and searches Pipedrive for people by that address. Then it merges the Pipedrive person ID back into the ticket data so every ticket “knows” who it belongs to.

Create clean notes from Zendesk comments. The workflow retrieves ticket comments via HTTP request, splits them into batches, and creates a note in Pipedrive for each relevant comment. When it’s finished, it stores a fresh “last run” timestamp for tomorrow.

You can easily modify the channel filter to include chat or web form tickets, or change how notes are formatted to match your sales team’s style. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Cron Trigger

This workflow runs daily and starts by capturing the last execution time.

  1. Add and open Daily 09:00 Trigger.
  2. Set Trigger Times to run at hour: 9.
  3. Connect Daily 09:00 Trigger to Fetch Prior Run Time.

Step 2: Connect Zendesk and Pull Updated Tickets

These nodes fetch updated Zendesk tickets since the last workflow run.

  1. Open Fetch Prior Run Time and keep the Function Code as provided to set lastExecution and executionTimeStamp.
  2. Open Pull Updated Tickets and set Operation to getAll.
  3. In Pull Updated Tickets, set Options → Query to =updated>{{ $json["lastExecution"] }}, Sort By to updated_at, and Sort Order to desc.
  4. Credential Required: Connect your zendeskApi credentials in Pull Updated Tickets.
  5. Connect Fetch Prior Run Time to Pull Updated Tickets.

Step 3: Filter Tickets and Prepare Email Search Data

This section verifies email-based tickets, extracts the sender address, and searches for matching Pipedrive people.

  1. Open Verify Email Channel and set the condition to ={{ $json["via"].channel }} equals email.
  2. Note the parallel branch: Verify Email Channel outputs to both Assign Search Address and Combine Pipedrive IDs in parallel.
  3. In Assign Search Address, set SearchEmail to ={{ $json["via"].source.from.address }} and enable Keep Only Set.
  4. In Remove Duplicate Emails, set Operation to removeDuplicates, Compare to selectedFields, and Fields to Compare to SearchEmail.
  5. In Find People by Email, set Resource to person, Operation to search, and Term to ={{ $json["SearchEmail"] }}.
  6. Credential Required: Connect your pipedriveApi credentials in Find People by Email.

The Idle Placeholder node exists for non-email tickets; you can keep it as-is for logging or expansion.

Step 4: Merge Pipedrive IDs and Retrieve Ticket Comments

This step merges Zendesk tickets with matched Pipedrive person IDs and collects ticket comments.

  1. In Map Essential Fields, set PipeDrivePersonId to ={{ $json["id"] }} and primary_email to ={{ $json["primary_email"] }}, with Keep Only Set enabled.
  2. Configure Combine Pipedrive IDs with Mode mergeByKey, Property Name 1 via.source.from.address, and Property Name 2 primary_email.
  3. In Pipedrive ID Present?, confirm the condition is ={{ $json["PipeDrivePersonId"] }} is not empty.
  4. Parallel branch note: Pipedrive ID Present? outputs to both Retrieve Ticket Comments and Merge Ticket Comments in parallel.
  5. In Retrieve Ticket Comments, set URL to =https://n8n.zendesk.com/api/v2/tickets/{{$json["id"]}}/comments and keep Authentication as predefinedCredentialType.
  6. Credential Required: Connect your zendeskApi credentials in Retrieve Ticket Comments.

⚠️ Common Pitfall: If Pipedrive ID Present? is false, data goes to Bypass Placeholder and comments will not sync. Ensure your email matching is accurate.

Step 5: Process Comments and Create Pipedrive Notes

This block splits comment arrays, filters recent comments, and creates Pipedrive notes.

  1. In Merge Ticket Comments, keep Join as inner and Mode as mergeByIndex.
  2. Open Batch Ticket Comments and set Batch Size to 1.
  3. In Split Comment Items, set Field to Split Out to comments.
  4. In Check Recent Comment, compare Value 1 ={{ $json["created_at"] }} to Value 2 ={{$item(0).$node["Fetch Prior Run Time"].json["lastExecution"]}}.
  5. In Create Pipedrive Note, set Resource to note and Content to =Message imported from Zendesk ------------------------------------------------ From {{$json["via"]["source"]["from"]["name"] ?? 'Zendesk user'}} ------------------------------------------------ {{$json["body"]}}.
  6. In Create Pipedrive Note → Additional Fields, set Person ID to ={{$item(0).$node["Batch Ticket Comments"].json["PipeDrivePersonId"]}}.
  7. Credential Required: Connect your pipedriveApi credentials in Create Pipedrive Note.

The Skip Placeholder node captures comments that don’t pass Check Recent Comment; keep it for auditing or add logging later.

Step 6: Store Latest Run Time

After comment processing completes, the workflow stores the execution timestamp for the next run.

  1. In All Items Processed?, confirm the condition checks ={{$node["Batch Ticket Comments"].context["noItemsLeft"]}} equals true.
  2. Ensure the true branch connects to Store Latest Run Time and the false branch loops back to Batch Ticket Comments.
  3. In Store Latest Run Time, keep the Function Code that sets staticData.lastExecution to $item(0).$node["Fetch Prior Run Time"].executionTimeStamp.

Step 7: Test and Activate Your Workflow

Run a manual test to verify Zendesk comments create notes in Pipedrive, then activate the workflow for daily runs.

  1. Click Execute Workflow and watch items move from Pull Updated Tickets through Create Pipedrive Note.
  2. Confirm that recent Zendesk comments produce Pipedrive notes with the expected content format.
  3. Verify that Store Latest Run Time runs after All Items Processed? returns true.
  4. Enable the workflow with the Active toggle so Daily 09:00 Trigger runs automatically.
🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Troubleshooting Tips

  • Zendesk credentials can expire or need specific permissions. If things break, check your Zendesk API token and admin role permissions first.
  • If you’re using Wait-like behavior (or any external API that responds slowly), processing times vary. Bump up batch size or add a short delay if downstream nodes fail on empty or incomplete responses.
  • Pipedrive note content can get noisy if you dump raw comments in. Clean up formatting in the Set step so you capture the “what changed” without walls of text.

Next Steps

If your team also needs the correct rep assigned before notes start flowing, Zendesk + Pipedrive: tickets assigned to the right owner pairs perfectly with this workflow.

For teams doing support plus lifecycle marketing, HubSpot + Zendesk: keep customer orgs up to date helps keep company records aligned across systems.

When you want ticket conversations visible where your team actually chats, Zendesk meets Slack for always updated ticket threads can reduce the “any update?” back-and-forth.

Need tighter collaboration between support and engineering? Zendesk meets Jira for tickets that stay in sync makes sure bug work and customer impact don’t drift apart.

Finally, if your delivery team lives in tasks and checklists, Zendesk + Asana: tickets that stay in sync turns issues into trackable work without manual re-entry.


Quick reference:

Quick Answers

What’s the setup time for this Zendesk Pipedrive sync automation?

About 30 minutes if your Zendesk and Pipedrive accounts are ready.

Is coding required for this ticket note sync?

No coding required. You’ll connect Zendesk and Pipedrive, then confirm the email field mapping and note format.

Is n8n free to use for this Zendesk Pipedrive sync workflow?

Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in Zendesk and Pipedrive plan limits (mainly API access on some tiers).

Where can I host n8n to run this automation?

Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.

Can I modify this Zendesk Pipedrive sync workflow for different use cases?

Yes, but keep the matching logic consistent. You can expand the “Verify Email Channel” check to include other channels, adjust the “Map Essential Fields” step to capture extra metadata (ticket status, priority), and rewrite the note body before the “Create Pipedrive Note” action. Common customizations include only syncing the most recent comment, adding a link back to the Zendesk ticket, and tagging notes so reps can filter them in Pipedrive.

Why is my Zendesk connection failing in this workflow?

Usually it’s expired credentials or an API token that doesn’t have access to tickets and comments. Regenerate the Zendesk API token, update it in n8n, and then re-test the “Pull Updated Tickets” and “Retrieve Ticket Comments” steps. If only some tickets fail, check rate limits and confirm the ticket channel filter isn’t excluding what you expected.

What volume can this Zendesk Pipedrive sync workflow process?

Plenty for most small teams: dozens of updated tickets per day is normal.

Is this Zendesk Pipedrive sync automation better than using Zapier or Make?

Often, yes. This workflow relies on saved timestamps, de-duplication, merging records by key, and batch processing of ticket comments, and those details matter when you don’t want duplicates or missed updates. n8n handles branching and loops cleanly, which means you can sync multiple comments per ticket without turning it into a fragile chain of zaps. You also get the option to self-host for unlimited executions, which is useful when ticket volume spikes. Zapier or Make can still be fine for a simple “new ticket, create note” flow, but daily incremental syncing is where n8n usually feels more stable. Talk to an automation expert if you’re not sure which fits.

Once this is running, the CRM stops being the “sales-only” view of the customer. It becomes the shared timeline everyone can trust.

Need Help Setting This Up?

Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.

Talk to Automation Expert →

Lisa Granqvist

Workflow Automation Expert

Expert in workflow automation and no-code tools.

×

Use template

Get instant access to this n8n workflow Json file

Copy and import json workflow into your n8n workflow

💬
Get a free quote today!
Get a free quote today!

Tell us what you need and we'll get back to you within one working day.

Get a free quote today!
Get a free quote today!

Tell us what you need and we'll get back to you within one working day.