# Connect Zendesk to HubSpot > Sync support tickets, contact records, and customer health data between Zendesk and HubSpot so every team has a complete view of the customer. **Canonical page:** https://tray.ai/connectors/zendesk-hubspot-integrations/ **Zendesk connector:** https://tray.ai/connectors/zendesk-integrations/ **Zendesk documentation:** https://tray.ai/documentation/connectors/service/zendesk **HubSpot connector:** https://tray.ai/connectors/hubspot-integrations/ **HubSpot documentation:** https://tray.ai/documentation/connectors/service/hubspot ## Overview Zendesk and HubSpot are two of the most widely used platforms in the modern customer stack — one running your support operations, the other driving sales and marketing. But without a direct integration, customer data lives in silos: support agents can't see deal history, and sales reps have no visibility into open tickets or CSAT scores. Connecting Zendesk and HubSpot through tray.ai gives you real-time, bidirectional data flow between your customer-facing teams. When Zendesk and HubSpot run independently, customer relationships pay the price. Sales teams close deals without knowing a prospect has three unresolved support tickets. Support agents handle escalations without knowing the customer's contract value or renewal date. Integrating them on tray.ai gives you a single source of truth across the entire customer lifecycle, from first marketing touch to post-sale support. Customer success teams can step in before churn happens. Sales can prioritize accounts with healthy support histories. Marketing gets the signal they need to keep frustrated customers out of promotional campaigns. The result is a measurably better customer experience and tighter alignment across revenue-generating teams. ## Use cases ### Bidirectional Contact and Company Sync Keep contact and company records aligned between HubSpot CRM and Zendesk without manual data entry. When a new contact is created in HubSpot — through a form fill, deal creation, or import — a corresponding Zendesk user and organization is automatically created or updated, and vice versa. Support agents always have accurate CRM context, and sales reps see current contact information. - Eliminate duplicate data entry across both platforms - Make sure support agents always have the latest CRM contact details - Prevent orphaned Zendesk users that don't map to HubSpot CRM records ### Ticket Activity Logged in HubSpot CRM Timeline Automatically log Zendesk ticket events — ticket creation, status changes, comments, and CSAT ratings — directly on the associated HubSpot contact or company timeline. Sales and customer success managers get full support visibility without leaving HubSpot, so they can engage customers knowing exactly what's happened on the support side. - Give sales and CS teams real-time support visibility inside HubSpot - Inform outreach by surfacing ticket sentiment and resolution history - Cut down on cross-platform logins just to gather customer context ### Escalate High-Value Customer Tickets to HubSpot Deals or Tasks When a Zendesk ticket is flagged as high-priority or escalated, automatically create a follow-up task, note, or deal stage update in HubSpot so the account manager is looped in immediately. This matters most for enterprise accounts, where a support failure can directly affect renewal outcomes. - Alert account managers the moment a VIP customer escalates an issue - Tie support escalations directly to deal or renewal pipeline activity - Cut churn risk by speeding up the loop between support and sales leadership ### Sync HubSpot Deal Stage Changes to Zendesk for Onboarding Triggers When a HubSpot deal moves to Closed Won, automatically create a Zendesk ticket or onboarding request, assign it to the right support queue, and populate it with deal metadata like contract value, product tier, and key contacts. The manual handoff between sales and customer success — at the worst possible moment to drop the ball — disappears. - Automate the sales-to-support handoff the moment a deal closes - Pre-populate onboarding tickets with accurate deal and contact data - Get new customers to first value faster by cutting setup delays ### CSAT Score Sync to HubSpot for Health Scoring Push Zendesk CSAT scores and satisfaction ratings into HubSpot as custom contact or company properties, where they feed into customer health scores, lifecycle stage updates, or NPS workflows. Teams can build HubSpot lists and workflows based on support satisfaction data to trigger proactive outreach or flag at-risk accounts. - Pull support satisfaction data into your HubSpot health scoring model - Automatically trigger re-engagement campaigns for customers with poor CSAT - Give customer success managers a quantified view of support experience by account ### Lead and Marketing Context Surfaced in Zendesk for Support Agents Enrich Zendesk ticket sidebars with HubSpot CRM data — lifecycle stage, deal value, marketing engagement score, and last campaign interaction — so support agents have full commercial context when responding to customers. Agents can prioritize tickets from high-value leads or at-risk accounts without switching tools. - Help support agents triage tickets with commercial context in mind - Surface lifecycle stage and deal value directly in the Zendesk ticket interface - Cut escalation response times for prospects and high-value customers ### Automate Support SLA Breach Notifications to HubSpot Owners When a Zendesk ticket breaches its SLA threshold, automatically notify the HubSpot deal or contact owner via task creation, email, or a Slack alert triggered through HubSpot workflows. No support breach affecting a customer goes unnoticed by the account owner. - Notify account owners instantly when a customer's SLA is breached - Create an auditable record of SLA events on the HubSpot contact timeline - Protect renewal conversations by staying ahead of support performance issues ## Templates ### New HubSpot Contact to Zendesk User Sync Automatically creates or updates a Zendesk user whenever a new contact is added or updated in HubSpot, keeping customer identity in sync across both platforms without manual effort. Connectors used: HubSpot, Zendesk ### Zendesk Ticket Created to HubSpot Timeline Activity Logs a new activity on the HubSpot contact timeline every time a Zendesk support ticket is created, updated, or closed, giving revenue teams full support visibility from within HubSpot. Connectors used: Zendesk, HubSpot ### HubSpot Closed Won Deal to Zendesk Onboarding Ticket When a deal reaches Closed Won in HubSpot, this template automatically creates a structured onboarding ticket in Zendesk, assigns it to the correct team, and populates it with deal data to eliminate manual handoffs. Connectors used: HubSpot, Zendesk ### Zendesk CSAT Score to HubSpot Contact Property Update Syncs Zendesk customer satisfaction scores to a custom HubSpot contact property after each ticket is resolved, enabling health scoring, lifecycle automation, and at-risk account identification inside HubSpot. Connectors used: Zendesk, HubSpot ### Zendesk Escalated Ticket to HubSpot Task and Owner Notification Creates a HubSpot task and notifies the assigned contact owner whenever a Zendesk ticket is escalated or hits a high-priority threshold, so account managers can step in before a support issue damages the customer relationship. Connectors used: Zendesk, HubSpot ### Bidirectional Company and Organization Sync Keeps HubSpot company records and Zendesk organizations in continuous sync, so account-level data like industry, tier, and renewal date stays accurate in both platforms for support and sales teams. Connectors used: HubSpot, Zendesk ## Challenges Tray.ai solves ### Deduplication Across Two Large Contact Databases Both Zendesk and HubSpot accumulate thousands of contact records over time, often with inconsistent email formats, duplicate entries, or mismatched naming conventions. A sync without deduplication logic can create duplicate users in Zendesk or ghost contacts in HubSpot, polluting both systems and undermining data trust. **How Tray.ai helps:** tray.ai's workflow logic lets you build deduplication steps using email normalization, fuzzy matching rules, and conditional branching. Before creating a new record in either system, the workflow searches for existing records by email or domain and decides whether to create, update, or skip — keeping both databases clean. ### Field Mapping Mismatches Between CRM and Support Schemas HubSpot and Zendesk use fundamentally different data models. HubSpot organizes data around contacts, companies, and deals; Zendesk structures data around users, organizations, and tickets. Custom properties in HubSpot rarely have natural equivalents in Zendesk, making field mapping a persistent source of integration failures. **How Tray.ai helps:** tray.ai has a visual field mapper and supports custom JavaScript or JSONPath transformations within workflows, so teams can map, reformat, and derive values across any field in either platform. You can translate HubSpot lifecycle stages into Zendesk tags, or convert Zendesk ticket priority levels into HubSpot custom numeric properties, without writing a full custom integration. ### Handling High-Volume Ticket Events Without Rate Limit Errors High-traffic Zendesk accounts can generate thousands of ticket events per hour — status changes, comments, and CSAT responses — which can quickly overwhelm HubSpot's API rate limits when every event triggers a CRM update. Left unmanaged, this leads to failed syncs, data lag, and incomplete HubSpot timelines. **How Tray.ai helps:** tray.ai handles API rate limit management natively, with built-in retry logic, exponential backoff, and queue-based execution to process every event reliably without overwhelming either API. Workflows can also be configured to batch updates or throttle event processing based on volume thresholds. ### Keeping Data in Sync Without Creating Infinite Update Loops Bidirectional integrations between Zendesk and HubSpot carry the risk of circular updates — a change in HubSpot triggers a sync to Zendesk, which fires a webhook back to HubSpot, which updates the record again. These loops create duplicated timeline events, inflated API usage, and corrupted field values. **How Tray.ai helps:** tray.ai workflows can implement loop prevention using timestamp comparison, a dedicated sync flag field, or source-of-truth routing rules. For example, a workflow can check whether the incoming change was initiated by the integration itself using a custom metadata field before deciding whether to propagate the update, fully preventing circular sync events. ### Authenticating and Maintaining Credentials for Both Platforms Securely Enterprise Zendesk and HubSpot instances often rotate API credentials, use OAuth with expiring tokens, or require scoped permissions that differ by team or environment. Manually managing authentication across multiple instances is a real operational risk — credentials expire and silently break production syncs. **How Tray.ai helps:** tray.ai's Universal Connector and centralized credentials manager let teams store, refresh, and reuse authenticated connections across all workflows from one place. OAuth token refresh is handled automatically, and role-based access controls keep credentials secure without exposing them to individual workflow builders. ## Learn more - Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/ - Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/ - Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/ - Book a demo: https://tray.ai/contact/