HubSpot Zendesk integration: what syncs, what doesn't and your options

Start with the question your team is trying to answer. If sales and account managers only need to see a contact's support history in HubSpot, the free integration may be enough. If tickets need to change HubSpot data, such as a company property or a deal stage, you need action flows, an app or a custom build.

1. Open the integration's install page and enter your Zendesk subdomain.
2. Authorize the connection in both Zendesk and HubSpot.
3. Zendesk creates three triggers, for new tickets, solved tickets and CSAT ratings, and a webhook called HubSpot Integration.
4. Edit the conditions of those triggers if you only want some tickets to reach HubSpot.

Zendesk documents a few limits. The integration is one-way, from Zendesk to HubSpot. Only the user's email address is synced, not the first or last name. Tickets are shown only on the contact timeline, not on company or deal records. You can change which tickets are sent by editing the trigger conditions, but you can't change the JSON payload. To turn the integration off, disable the three triggers.

Action flows are Zendesk's builder for multi-step automations that reach external systems. The HubSpot connector adds these actions:

• Create and update contacts, companies, deals and tickets in HubSpot.
• Look up contacts, companies, deals and tickets, and look up users.
• Look up a contact by Contact ID or email. If you give both, Contact ID takes precedence.
• Connect with OAuth 2.0 from 'External actions' in the step sidebar. Zendesk recommends a dedicated service account and refreshes tokens automatically.

Action flows use action credits. Zendesk lists 100,000 actions a month for Suite Professional and 225,000 for Suite Enterprise, sends an email at 80% and 100% of the allowance, and sells more in units of 100,000. Admins can see usage in Admin Center under Account, then Usage, then Summary. Allowances and plan availability change, so check them in your own account before you build on action flows.

The Zendesk Marketplace lists a Data sync by HubSpot app that it describes as a bi-directional, real-time sync between HubSpot and Zendesk. Installing it needs a HubSpot Super Admin or a user with App Marketplace permissions, who enters the Zendesk subdomain, authorizes the connection and chooses what to sync. Third-party apps such as HubSpot CRM Connect add their own features. Marketplace listings are marketing pages, so check which records and fields an app really syncs on its setup screen before you rely on it.

HubSpot's data sync documentation explains how two-way syncs match records: by default, contacts are matched by email and companies by name or domain, and only contacts with a valid email address are synced. Clean up duplicate contacts and missing emails before you turn on a two-way sync, or the sync will copy the mess into both tools.

A custom build gives you full control, for example showing open tickets on HubSpot company records, which the free integration can't do. Here is a common pattern, described as steps. It isn't a TascaLab case study.

1. Trigger: a Zendesk trigger with the Notify by > Active webhook action sends the ticket ID and requester email to n8n or Make when a ticket is created or its status changes.
2. Verify: the workflow checks the X-Zendesk-Webhook-Signature header, so only real Zendesk requests are processed.
3. Look up: it finds the HubSpot contact by email through the CRM API, then the company the contact is associated with.
4. Update: it writes the ticket count or latest status to a company property, which HubSpot lists, reports and workflows can use.
5. Handle errors: it waits and retries on HTTP 429, since both Zendesk and HubSpot limit API requests.

For the other direction, a HubSpot workflow can call your endpoint with the 'Send a webhook' action, which HubSpot lists for Data Hub Professional and Enterprise and which only accepts HTTPS URLs. On the Zendesk side, use OAuth rather than API tokens. Zendesk stopped letting existing accounts create new API tokens on October 27, 2026, and all API tokens stop working on April 30, 2027. OAuth clients created on or after April 30, 2026 get access tokens that expire after 30 minutes by default, so the integration needs refresh-token handling.

TascaLab connects Zendesk and HubSpot through APIs, webhooks, n8n and Make, on top of the tools you already use. Custom Automation projects cost from $1,200. Most setups take 1 to 3 weeks, and every project includes basic documentation and 30 days of post-launch support. You can start with a free 30-minute Health Check call.