How to Integrate Zendesk with HubSpot (Step by Step)

The single most important thing to get straight before you start: there isn't one "Zendesk HubSpot integration." There are two official connectors, built by two different companies, and they do different jobs. Mixing them up is the source of nearly every "wait, why isn't this syncing?" support thread. We'll cover both, explain which one you actually want, and point to the HubSpot and Zendesk primary docs as we go. Labels change periodically, so confirm them in your own accounts.

The two integrations (read this first)

It's worth 90 seconds to understand the landscape, because picking the wrong app wastes an afternoon.

Despite the names, the connector that produces the "see Zendesk tickets on the HubSpot contact" experience most people are after — Zendesk Support for HubSpot — is the one built and maintained by Zendesk, even though you find it on the HubSpot App Marketplace too. HubSpot's own connector is Data Sync, which is about keeping records (contacts, companies, tickets) mirrored as database objects rather than posting timeline activity. The HubSpot Marketplace listing for the timeline app states it plainly: it's "Built by Zendesk." Keep that distinction in your head and the rest of this is easy.

For most teams the answer is: start with Zendesk Support for HubSpot (the timeline app) for visibility, and add Data Sync only if you genuinely need contact/company records mirrored both ways. You can run both.

Before you start: what you'll need

• A Zendesk admin. Authorizing the connection and letting it create triggers/webhooks requires an admin role in Zendesk.
• A HubSpot Super Admin (or App Marketplace permissions). HubSpot requires Super Admin or explicit App Marketplace permissions to install any app.
• A paid Zendesk Suite plan. The Zendesk-built connector is listed as compatible with Suite Team and above; it isn't available on the lightest legacy plans.
• Your Zendesk subdomain handy (the yourcompany in yourcompany.zendesk.com) — the OAuth flow asks for it.
• A decision on scope. Timeline visibility only? Or full record sync too? That determines whether you install one connector or both.

Step 1 — Install the Zendesk integration from the HubSpot App Marketplace

We'll set up the timeline connector first, because it delivers the most-wanted outcome (support context on the contact record) with the least configuration.

1. In HubSpot, click the Marketplace icon in the main top navigation bar, then choose App Marketplace.
2. Search for Zendesk and open the listing built by Zendesk (the "Zendesk Support for HubSpot" app — the one that adds ticket activity to the CRM timeline).
3. Click Install app / Connect app to start the flow.

Behind the scenes this hands you to Zendesk's own integration service (hubspot.zendesk-integrations.com) to complete authorization — which is exactly why the connector is Zendesk-built even though you launched it from HubSpot's marketplace. There's no code, no snippet, and nothing to paste into Zendesk manually.

Step 2 — Connect and authorize (OAuth, both admins)

This is the handshake that links the two accounts. You'll bounce between Zendesk and HubSpot consent screens:

1. Enter your Zendesk subdomain when prompted.
2. Authorize the Zendesk app — log into Zendesk as an admin and approve access.
3. Allow access to the HubSpot app — approve the HubSpot side as a Super Admin.
4. Authorize Zendesk to use your data to finish the OAuth grant.

Because the grant touches both products, do this with both an active Zendesk admin and a HubSpot Super Admin session. If you hit a permissions error, it's almost always a non-admin trying to approve one side.

When authorization completes, the connector automatically provisions the plumbing inside Zendesk — you don't build it. Per Zendesk's setup doc, it creates three triggers — [Hubspot Integration] - Ticket Created, [Hubspot Integration] - Ticket Solved, and [Hubspot Integration] - Ticket CSAT Rating Submitted — plus a single webhook named HubSpot Integration. Those triggers fire on the matching events and the webhook pushes them to HubSpot in near real time. You can see (and audit) those auto-created triggers in the Zendesk Triggers admin, under Admin Center → Objects and rules → Business rules → Triggers:

![First-hand view of the Zendesk Triggers admin in Admin Center — the auto-created "[Hubspot Integration]" triggers appear in this list alongside your other ticket triggers.](/images/grid/6a368cc5c44962509174f7f6?w=900)

Here's the honest nuance worth stating plainly: this integration is installed and primarily configured on the HubSpot side (the App Marketplace plus your HubSpot timeline view). On the Zendesk side, what you'll see afterward is the auto-created triggers and webhook — and that's also where any Zendesk-built apps you install are managed, under Admin Center → Apps and integrations. The screenshot below shows that Zendesk apps admin area for reference; it's where you'd verify or remove Zendesk-side app components, not where you configure the HubSpot connection itself.

Step 3 — Configure ticket sync to the contact timeline

Once connected, ticket activity starts flowing one-way from Zendesk into HubSpot. There's intentionally little to configure here — and one limitation to know up front.

What lands on the HubSpot contact record (matched by the requester's email, with a new contact auto-created if one doesn't exist):

• The ticket title and status
• The full conversation history
• A direct link back to the ticket in Zendesk
• The CSAT rating (once submitted)
• Group / assignee and any applied tags

To view it in HubSpot:

1. Go to Contacts and open any contact.
2. Open the Activities tab.
3. Click Filter activity, then under Integrations tick Zendesk so ticket events show in the timeline.

The limitation to plan around: the Zendesk doc is explicit that ticket activity appears only on contact timelines — not on company or deal records — and that you can't customize which ticket fields appear. If your sales team works primarily from company or deal views, they won't see tickets there. That's a real constraint, not a configuration you missed.

Step 4 — (Optional) Add contact and company sync with Data Sync

If you need the records themselves aligned — not just timeline activity — install Data Sync, the connector built by HubSpot. This is the piece that keeps your CRM and helpdesk databases mirrored.

1. In HubSpot, open the App Marketplace again, search Zendesk, and choose the Data Sync option (HubSpot-built). Click Install and sign into Zendesk to authorize.
2. After connecting, configure the sync: choose the sync direction, map fields between Zendesk and HubSpot properties, set conflict resolution rules (which system wins on a clash), and apply filters to limit which records sync.
3. Turn the sync on.

What Data Sync covers, per HubSpot's documentation:

• Zendesk users ↔ HubSpot contacts — two-way
• Zendesk organizations ↔ HubSpot companies — two-way
• Zendesk tickets → HubSpot tickets — one-way (per HubSpot's Data Sync app listing, which notes archived tickets are excluded; confirm the current behavior on the Data Sync listing, as HubSpot occasionally revises what each object syncs)

The cost gotcha: syncing default fields works on free HubSpot, but mapping custom properties (e.g. pushing a HubSpot "plan tier" or "renewal date" onto a Zendesk user/organization field) requires Operations Hub / Data Hub Starter or higher. If custom mappings silently don't appear, your plan tier is usually why.

Step 5 — Test the connection

Don't trust it until you've watched a ticket make the round trip:

1. Create a test ticket in Zendesk from a known email that exists (or should exist) in HubSpot.
2. In HubSpot, open that contact → Activities → Filter activity → Integrations → Zendesk and confirm the new ticket appears on the timeline.
3. Solve the ticket in Zendesk and confirm the status updates on the timeline; submit a CSAT response and confirm the rating shows.
4. If you set up Data Sync, edit a contact field on the synced side and confirm it propagates after the next sync cycle (it's periodic, not always instant).

If nothing appears: verify the requester's email matches a HubSpot contact (matching is email-based), confirm the auto-created triggers and webhook still exist in Zendesk, and check you authorized with the right admin accounts.

A note on legacy setups and visitor context

If you inherited an older configuration, a few things are worth a sanity check:

• The connector landscape consolidated. Older write-ups reference assorted third-party apps and a legacy version of the Zendesk app; today the two official paths above (Zendesk-built timeline app + HubSpot-built Data Sync) are the supported ones. If you're on an unmaintained third-party connector, plan a migration.
• Visitor / CRM context inside Zendesk. The native timeline app pushes data Zendesk → HubSpot. If your goal is the reverse — surfacing HubSpot CRM or marketing context inside the Zendesk agent workspace so agents see deal stage or plan tier — that's a separate capability (Data Sync field mappings, a sidebar app, or a purpose-built layer), not something the timeline connector does on its own.
• Clean your identifiers first. Because matching is email-based, duplicate or inconsistent emails create duplicate contacts. Tidy key identifiers before a broad rollout.

Permissions and limitations at a glance

• Permissions: HubSpot Super Admin or App Marketplace permissions to install; a Zendesk admin to authorize and let triggers/webhooks be created.
• Direction: the timeline connector is one-way (Zendesk → HubSpot). Data Sync is two-way for users/orgs, one-way for tickets.
• Placement: tickets show on contact timelines only — not company or deal views.
• Customization: you can't change which ticket fields appear in the timeline.
• User detail: the timeline connector's user sync carries only the email address (first/last name don't sync via that path) — Data Sync is the route for richer field mapping.
• Plan gates: the Zendesk connector needs a paid Zendesk Suite plan; custom Data Sync mappings need HubSpot Operations Hub / Data Hub Starter+.
• Quality bar: the timeline app carries a middling marketplace rating (~2.2/5 across reviews) — most complaints are about the one-way, contact-only, non-customizable scope above. Set expectations accordingly: it's a visibility tool, not a deep two-way bridge.

Troubleshooting common issues

Most setup problems trace back to one of a handful of causes. Before you assume the connector is broken, check these:

• Tickets aren't showing on the contact timeline. First, confirm you've actually enabled the Zendesk filter under Contacts → a contact → Activities → Filter activity → Integrations — events are present but hidden until you tick it. Second, remember matching is by email: if the ticket requester's email doesn't match a HubSpot contact (and auto-creation is restricted), nothing lands. Third, the three [Hubspot Integration] triggers must still exist and be active in Zendesk — if someone deactivated or deleted them, events stop flowing.
• Duplicate HubSpot contacts after connecting. This happens when the same person exists under different email addresses in Zendesk vs HubSpot. The timeline app auto-creates a contact from the requester's email, so mismatched emails produce duplicates. Clean up email consistency (or use Data Sync with a clear matching rule) before a large backfill.
• "Permission denied" during authorization. The OAuth grant needs an admin on both sides simultaneously — a Zendesk admin and a HubSpot Super Admin (or a user with App Marketplace permissions). A non-admin approving one side is the most common cause.
• Custom field mappings won't save in Data Sync. Custom mappings require HubSpot Operations Hub / Data Hub Starter or higher — on free HubSpot you're limited to default-field sync. The save simply won't stick on an unsupported tier.
• Wrong objects syncing in Data Sync. Data Sync direction and object selection are configured per object during setup; if companies sync but tickets don't (or vice versa), re-open the Data Sync configuration and confirm each object's sync is switched on and pointed the right direction.

When in doubt, the connector's own logs (Zendesk webhook activity, and HubSpot's sync health view) tell you whether events are firing and where they're failing.

Where AI fits in

Connecting Zendesk and HubSpot solves a visibility problem: now the context exists in one place. But context sitting on a timeline still needs a human to read it, interpret it, and act. That's the next gap — and where an AI agent layer is useful.

To be clear about what Macha is: Macha is an AI agent that runs on top of your existing Zendesk — not a helpdesk, not a CRM, and not a replacement for either. Once your CRM and marketing context is flowing into the support picture, an AI agent can actually use it: read an incoming ticket, pull the customer's plan, recent orders, or deal stage from the connected context, and answer account- and order-level questions automatically — the "what plan am I on / where's my order / when does my contract renew" volume that otherwise pulls an agent away to go look things up. When it isn't confident, it hands off to a human with that context attached, and keeps the ticket housekeeping (tags, status, routing) tidy along the way.

The honest framing: it's another layer to configure, and it's only as good as the data and knowledge you connect. On cost, Macha bills per AI action — each automated step it takes, like drafting a reply, tagging, or looking up an account — not per resolution, because most automation is work done along the way rather than a tidy one-to-one "ticket solved." If a chunk of your Zendesk volume is repetitive account questions that the right connected context could answer, that's the line where an AI agent starts to pay off. See Macha on Zendesk for how it plugs in, and you can try it with a 7-day free trial, no credit card required.

Frequently asked questions

Who builds the Zendesk HubSpot integration — Zendesk or HubSpot? Both, depending on which one you mean. The connector that posts Zendesk ticket activity onto the HubSpot contact timeline ("Zendesk Support for HubSpot") is built and maintained by Zendesk, even though it's listed on the HubSpot App Marketplace. HubSpot's own connector is Data Sync, which mirrors records (contacts, companies, tickets) between the two systems. Most "see my tickets in HubSpot" use cases want the Zendesk-built timeline app.

Where do I install it? The timeline app installs from the HubSpot App Marketplace (Marketplace icon → App Marketplace → search Zendesk → Install), then completes authorization through Zendesk's integration service. Data Sync installs the same way from HubSpot's App Marketplace.

Is the ticket sync one-way or two-way? The timeline connector is one-way: Zendesk ticket events flow into HubSpot. HubSpot's Data Sync is two-way for users↔contacts and organizations↔companies, and one-way (Zendesk → HubSpot) for tickets.

Why don't Zendesk tickets show on my HubSpot company or deal records? By design. Zendesk's documentation states ticket activity appears only on contact timelines, not on company or deal views, and you can't customize which fields appear. If sales works from company/deal views, factor that in.

What permissions do I need? A HubSpot Super Admin (or App Marketplace permissions) to install, and a Zendesk admin to authorize the connection and allow the auto-created triggers and webhook. Authorizing as a non-admin on either side is the usual cause of setup errors.

Do I need a paid plan? The Zendesk-built timeline app needs a paid Zendesk Suite plan. Basic Data Sync of default fields works on free HubSpot, but custom field mapping requires HubSpot Operations Hub / Data Hub Starter or higher.

Can agents see HubSpot CRM data inside Zendesk? The native timeline app only pushes data into HubSpot. To surface HubSpot context inside the Zendesk agent workspace, you'd use Data Sync field mappings, a sidebar app, or an AI agent layer that reads the connected context — that's a separate setup from the timeline connector.

The bottom line

A Zendesk HubSpot integration is straightforward once you know there are two connectors built by two companies: Zendesk Support for HubSpot (Zendesk-built) pushes ticket events onto the HubSpot contact timeline one-way, and Data Sync (HubSpot-built) keeps contacts, companies, and tickets mirrored as records. Install the timeline app from the HubSpot App Marketplace, authorize with OAuth as both a Zendesk admin and a HubSpot Super Admin, let it auto-create the Zendesk triggers and webhook, then view tickets under Contacts → Activities → Filter activity → Integrations → Zendesk. Add Data Sync if you need true record sync, mind the plan gates for custom fields, and remember the timeline app is contact-only and non-customizable by design. For the helpdesk fundamentals underneath all this, see our explainer on the Zendesk ticketing system, and for the sibling CRM connection, how to integrate Zendesk with Salesforce.

Setup verified against HubSpot and Zendesk official documentation, June 2026. Both products revise their UIs and plan gates periodically — confirm labels and tiers in your own accounts before relying on them.