Assign new Zendesk tickets to the right Pipedrive contact owner

Checks Zendesk every few minutes and automatically assigns new tickets to the matching contact owner in Pipedrive.

How the work actually flows

It branches. Exactly one path is taken; runs once per each new ticket.

Pattern: Exclusive Choice (4)

flowchart TD trig(["scheduled check for new tickets"]):::trigtime s0[["Match ticket to contact by email"]]:::mi s1[("Look up contact owner")]:::store trig --> s0 s0 --> s1 gx{"× contact owner found"}:::gate s1 --> gx p00["Reassign ticket to owner"]:::task gx -->|"owner found"| p00 p10["Add note to ticket"]:::task gx -->|"no owner found"| p10 p00 --> out p10 --> out out[/"ticket assigned to right owner"/]:::out pay{{"faster ticket routing"}}:::pay out --> pay s1 -. "failures recorded, run continues" .-> out classDef task fill:#e7f6fe,stroke:#34b8f0,color:#2c2a29 classDef svc fill:#f6f8fa,stroke:#7c8795,color:#2c2a29 classDef mi fill:#e7f6fe,stroke:#0079a8,color:#2c2a29,stroke-width:2px classDef human fill:#fff,stroke:#0079a8,color:#0079a8 classDef store fill:#f6f8fa,stroke:#0079a8,color:#2c2a29 classDef trig fill:#00a4eb,stroke:#0079a8,color:#fff,font-weight:bold classDef trigtime fill:#00a4eb,stroke:#0079a8,color:#fff,font-weight:bold classDef trigdata fill:#8ad4f5,stroke:#0079a8,color:#06314c,font-weight:bold classDef gate fill:#fff,stroke:#e8a23d,color:#6b4708,font-weight:bold classDef out fill:#1f9d6b,stroke:#167a53,color:#fff,font-weight:bold classDef pay fill:#06314c,stroke:#021f33,color:#fff
Starts itRuns once per itemA record or sheetOne path onlyResultPayoff
Build size
Advanced

A larger build with multiple systems, AI reasoning, and custom rules.

Business functions
CRM & Sales PipelineCustomer Support & Ticketing
Connects
ZendeskPipedrive

The problem it solves

New support tickets come in through Zendesk, but manually figuring out which Pipedrive contact and account owner should handle each one takes time and slows down response. Tickets can sit unassigned while someone tracks down who actually owns the relationship.

Who it fits

Sales and support teams using both Zendesk and Pipedrive who need tickets routed to the right account owner.

How it works

  1. Runs on a set schedule to check for new tickets
  2. Zendesk tickets are matched to a contact by email
  3. Pipedrive is checked for who owns that contact
  4. The ticket is reassigned to that contact owner
  5. If no match is found, a note is added instead
What you get

Tickets landing with the right account owner

Every new support ticket lands with the account owner who already knows that customer, keeping your sales and support teams on the same page.

What you get

Zendesk tickets automatically assigned to the correct Pipedrive contact owner.

What you need

A Zendesk account and a Pipedrive account, using the same email addresses.

We can build this. But should you?

The hard question is not how to build it. It is whether this is the right thing to build first.

That is what a Fractional Chief AI Officer figures out with you, before anyone writes a line of code.

Let's Talk Strategy

Related automations

Back to the AI Playbook