How Do You Connect Pipedrive to Zendesk? Native App vs AI Agent Custom Tool (2026)

You can connect Pipedrive to Zendesk two ways: Pipedrive's own Zendesk app, which matches people by email and shows up to 20 Zendesk tickets on a Pipedrive record, or a Macha Custom Tool that lets your AI agent look up or update the Pipedrive deal from inside the ticket. The first gives human agents shared visibility. The second gives the AI agent something it can act on.

Framing first. Macha runs on top of the Zendesk you already use. It's an AI-agent layer, not a Zendesk or Pipedrive replacement. Your team keeps working in Zendesk; Macha reads the ticket, reasons, and reaches into Pipedrive to answer or act.

What does the native Pipedrive Zendesk integration do?

The native app is built by Pipedrive and listed in the Pipedrive marketplace, which describes it as free or free with some usage limits. Inside Zendesk, a Pipedrive panel shows the deal title and status, deal value and currency, and deal creation date, and a rep can create a deal from the ticket. Inside Pipedrive, the person, deal and organization views show up to 20 Zendesk tickets with their status, and a rep can open a ticket from a deal (Pipedrive's help article). Everything joins on the requester's email address. If all you need is passive cross-visibility for human agents, that may be enough.

Where does the native integration stop?

• It's shared visibility, not action. It puts deal data on the screen. It doesn't let an AI agent decide to look up a deal mid-conversation, pass the right parameters and reason over the result, or update a deal from what happened in the ticket.
• It's capped and partial. Pipedrive's own FAQ calls it "two-way and contextual" with "no data overwrite, just visibility," so it isn't a field sync. It shows up to 20 tickets per record, and email matching fails when the requester isn't the deal's contact person (Pipedrive's workaround is to add them as a deal participant).
• It's fixed. You get the panel the app exposes, not the specific query or write your workflow needs, such as "what stage is this customer's deal in?" or "add a note to the deal from this ticket."

For a lot of teams, the shared panel is fine. For anyone who wants their AI agent to actually use Pipedrive, there's a lighter, more flexible path.

Why would you want an AI agent to use Pipedrive live?

The valuable version of this integration is the agent doing the work. A customer emails Zendesk; the agent recognizes them, looks up their live Pipedrive deal by email, and answers with the right context ("I can see you're evaluating our Pro plan, let me get you a proper answer") or writes a note back to the deal so the rep sees what support handled. Macha doesn't ship a prebuilt Pipedrive connector, so this runs through a Custom Tool, grounded in live Pipedrive data rather than a capped panel.

How do you connect Pipedrive to Zendesk with a Custom Tool?

A Custom Tool is a single action you define once and point at Pipedrive's REST API. No marketplace app, no code.

1. Point it at the Pipedrive API. Pipedrive's API accepts an API token or OAuth 2.0. For a direct integration, the token goes in the x-api-token request header (Pipedrive's API docs). Note that each user has one active token, and it carries that user's full data access, so create it under a dedicated integration user. The built-in Sidekick can scaffold the request from a plain-English description if you'd rather not fill in the form.

2. Define the action. Give it a label and a description the AI uses to decide when to call it, for example "Get the Pipedrive deal stage, value, and owner for a customer by email." Set the method and URL (a search or GET against the Pipedrive persons or deals API, with an {{email}} placeholder), and choose Read or Write. A lookup is a Read; adding a note or updating a deal is a Write, which requires confirmation before it runs.

3. The agent uses it live. Once the tool exists, the agent calls it mid-ticket, passes the customer's email, and reasons over the Pipedrive record it gets back, either personalizing the reply or logging the outcome to the deal.

How do you keep Pipedrive writes safe?

Because a Custom Tool can reach into Pipedrive, the guardrails matter. Read tools (lookups) run freely; Write tools (add a note, update a deal, change a field) require confirmation. Each tool is scoped to one action, permissioned per agent, and every call is audited. The Pipedrive token or OAuth grant lives in the tool's configuration, so secrets never appear in the conversation.

Teams usually build a few Pipedrive tools and group them (a deal lookup, an "add note to deal," a "flag account") alongside tools for their other systems.

Should you use the native app or a Custom Tool?

• Use Pipedrive's Zendesk app if you just want deals visible in the ticket for human agents and tickets visible on the deal, and the 20-ticket cap and email matching aren't a problem.
• Use a Custom Tool when you want your AI agent to look up live Pipedrive data or update a deal from the ticket, you need a specific query or write the app doesn't expose, or you'd rather not be capped. The two can coexist.

What else can the agent do once it reaches Pipedrive?

The same pattern covers more: read the deal stage before answering, check the value and owner to route a high-value prospect, add a support note to the deal timeline, update a custom field from the ticket, or flag a stalled account for the rep. Custom Tools aren't Pipedrive-specific either, so the same approach connects your billing system, data warehouse or internal API. See the Custom Tools integration directory for 200+ tools, or the full pillar on building custom Zendesk integrations.

How do you get started?

Pipedrive's app puts deals on the screen for humans. A Custom Tool puts Pipedrive in your AI agent's hands: live lookups and confirmed updates, decided in context, with no ticket cap and no code. Macha is the done-for-you option: the Macha team analyzes your past tickets, builds and tests the Pipedrive tool, the knowledge base and the agent, and runs it in safe mode, with drafts as internal notes, until the drafts are right. That's included on the trial and every plan at about $0.40 a ticket, which includes setup and a dedicated success manager who handles your changes, such as a new deal field to read. See how Custom Tools work, browse the integration directory, or start a free trial ($50 of usage, no credit card) and wire up your first Pipedrive tool.

Frequently asked questions

Does Zendesk have a native Pipedrive integration? Yes. Pipedrive builds a Zendesk app that shows Pipedrive deal data on the Zendesk ticket and up to 20 Zendesk tickets on the Pipedrive record, matched by the requester's email. It's built for shared visibility, not a field sync. A Custom Tool adds live, agent-driven lookups and updates with no cap.

Do I need an engineer to connect Pipedrive to Zendesk this way? No. The Macha team builds and tests the Pipedrive tool for you as part of setup, included on the trial and every plan. If you'd rather build it yourself, you describe the action in plain English and Macha's Sidekick scaffolds the Pipedrive request, auth and parameters. Technical teams can go deeper with full control over the API call, headers and response mapping.

Can the agent update Pipedrive, or only read it? Both. Reads (deal lookups) run freely; writes such as adding a note or updating a deal require a confirmation step, and you control which agents can use them.

Is it secure? Yes. The tool is scoped to a single action, permissioned per agent, authenticated with a Pipedrive API token or OAuth, and every call is audited.

Why doesn't the native app find some of my tickets? It matches on email. If the Zendesk requester isn't the deal's contact person in Pipedrive, the ticket won't appear on the deal until you add that person as a deal participant.