Intercom + Zendesk
Connect Intercom and Zendesk to Unify Customer Support and Messaging
Automate ticket creation, sync customer data, and keep support running smoothly across both platforms with tray.ai.
Why integrate Intercom and Zendesk?
Intercom and Zendesk are two of the most widely used customer-facing platforms in any modern support stack. Intercom excels at real-time messaging and proactive customer engagement, while Zendesk handles ticketing and helpdesk workflows. Together, they cover the full lifecycle of customer support, from the first chat message to formal ticket resolution. Integrating the two eliminates the data silos and manual hand-offs that slow down support teams and frustrate customers.
Automate & integrate Intercom & Zendesk
Use case
Automatic Ticket Creation from Intercom Conversations
When a customer conversation in Intercom reaches a certain tag, keyword, or escalation threshold, tray.ai automatically creates a corresponding ticket in Zendesk — complete with conversation history, customer details, and priority level. No more copy-pasting conversation context into a new ticket. Support agents in Zendesk can start working the issue immediately, with full context already in place.
Use case
Bi-Directional Customer Profile Sync
Customer attributes updated in Intercom — such as plan type, company name, or custom user data — are automatically reflected in the corresponding Zendesk user or organization record, and vice versa. Both platforms stay in agreement on who the customer is and what their current status is. Support agents always have accurate, up-to-date context without switching tools or making manual updates.
Use case
Zendesk Ticket Status Updates Reflected in Intercom
When a Zendesk ticket is resolved, updated, or closed, tray.ai pushes a status update back into the linked Intercom conversation — automatically notifying the customer or updating the conversation thread. Customers are informed in the channel where they originally reached out. Intercom-based customer success teams can also track resolution progress without logging into Zendesk.
Use case
Shared Tagging and Labeling Across Platforms
Tags applied in Intercom — such as 'billing issue,' 'bug report,' or 'enterprise customer' — can be automatically mapped to the corresponding Zendesk ticket tags, keeping categorization consistent across both systems. This makes cross-platform analytics far more reliable. Teams can build dashboards and SLA workflows that draw from consistent data regardless of which tool originated the interaction.
Use case
New Zendesk Tickets Triggering Intercom Outreach
When a Zendesk ticket is created for an existing Intercom user — through a web form submission or email — tray.ai can automatically trigger a proactive Intercom message to acknowledge receipt and set expectations. The customer feels heard right away, even before an agent picks up the ticket. It bridges the gap between the formal ticketing process and the conversational experience customers prefer.
Use case
Escalation Routing Based on Customer Segment or Plan
Using customer data from Intercom — such as subscription tier or account health score — tray.ai can route new Zendesk tickets to the appropriate support queue, group, or agent automatically. Enterprise or high-value customers get fast-tracked to specialized teams without any manual triage. Your highest-priority customers consistently receive the level of service they expect.
Use case
Consolidated Support Reporting Across Both Platforms
tray.ai can pull conversation volume, CSAT scores, and resolution data from both Intercom and Zendesk, then push the unified dataset into a BI tool or data warehouse for consolidated reporting. Support leaders get a single view of team performance across both channels without manually exporting and merging spreadsheets. Trend analysis, agent productivity, and customer satisfaction metrics become much easier to track at scale.
Get started with Intercom & Zendesk integration today
Intercom & Zendesk Challenges
What challenges are there when working with Intercom & Zendesk and how will using Tray.ai help?
Challenge
Mapping Inconsistent Data Models Between Platforms
Intercom and Zendesk use fundamentally different data structures. Intercom organizes around 'conversations' and 'contacts,' while Zendesk uses 'tickets' and 'users.' Mapping fields like priority, status, and custom attributes between the two without data loss or corruption is a real technical challenge when building a custom integration.
How Tray.ai Can Help:
tray.ai's visual workflow builder includes flexible field mapping and data transformation tools that let teams translate Intercom's data model into Zendesk's schema — and back — without writing custom code. Built-in data helpers handle type casting, null checks, and conditional logic to keep data clean throughout.
Challenge
Avoiding Infinite Update Loops Between Systems
When both platforms trigger on updates, a change in Zendesk can update Intercom, which triggers another update back to Zendesk — an infinite loop that floods both systems with redundant API calls and corrupts records.
How Tray.ai Can Help:
tray.ai handles this through conditional branching and state management within workflows. Teams can configure checks that detect whether a record was last modified by the integration itself and skip re-processing, cleanly breaking any potential sync cycle.
Challenge
Maintaining a Reliable Conversation-to-Ticket Link
Linking an Intercom conversation to its corresponding Zendesk ticket — and keeping that association accurate over time as tickets are merged, reopened, or cloned — is difficult to manage without a dedicated integration layer.
How Tray.ai Can Help:
tray.ai workflows can store and retrieve cross-platform reference IDs using data storage connectors or by writing the Zendesk ticket ID back into an Intercom conversation attribute. This creates a persistent, queryable link between records that stays accurate throughout the ticket lifecycle.
Challenge
Handling API Rate Limits During High-Volume Syncs
Both Intercom and Zendesk impose API rate limits that can throttle high-volume syncs — particularly during bulk backfills, peak support periods, or when running frequent scheduled jobs across large customer bases. Unmanaged rate limiting causes dropped records and incomplete syncs.
How Tray.ai Can Help:
tray.ai's workflow engine has built-in retry logic, configurable delays, and rate-limit-aware execution that automatically backs off and retries failed API calls. Teams can also paginate large dataset syncs across multiple workflow runs to stay within both platforms' rate limits.
Challenge
Keeping Custom Fields and Evolving Schemas in Sync
Both Intercom and Zendesk support custom fields that change as business needs evolve. When a new custom field is added to one platform, the integration needs to be updated to map it to the other — otherwise data silently fails to sync, and trust in the integration erodes over time.
How Tray.ai Can Help:
tray.ai makes it straightforward to update field mappings through the visual workflow editor without redeploying or rebuilding the entire integration. Teams can also add notification steps that alert an admin when an unmapped field is detected, so schema changes get caught and addressed before they become a problem.
Start using our pre-built Intercom & Zendesk templates today
Start from scratch or use one of our pre-built Intercom & Zendesk templates to quickly solve your most common use cases.
Intercom & Zendesk Templates
Find pre-built Intercom & Zendesk solutions for common use cases
Template
Escalate Intercom Conversation to Zendesk Ticket
Monitors Intercom for conversations tagged with a specified escalation label or assigned to a particular inbox, then automatically creates a fully populated Zendesk ticket with the customer profile, conversation transcript, and assigned priority.
Steps:
- Trigger: Intercom conversation is tagged 'escalate' or moved to a designated inbox
- Action: Fetch full conversation transcript and customer profile from Intercom
- Action: Create a new Zendesk ticket with conversation content, user details, and mapped priority level
Connectors Used: Intercom, Zendesk
Template
Sync Zendesk Ticket Resolution Back to Intercom
When a Zendesk ticket is marked as solved or closed, this template finds the linked Intercom conversation, posts an automated status update to the customer, then closes or tags the Intercom thread accordingly.
Steps:
- Trigger: Zendesk ticket status changes to 'Solved' or 'Closed'
- Action: Look up the associated Intercom conversation ID stored on the ticket
- Action: Send a resolution message to the customer in Intercom and update conversation tags
Connectors Used: Zendesk, Intercom
Template
Keep Customer Profiles in Sync Between Intercom and Zendesk
Runs on a scheduled interval or event-driven trigger to compare and synchronize user attributes — including name, email, company, plan, and custom fields — between Intercom contacts and Zendesk users, resolving conflicts and filling in missing data.
Steps:
- Trigger: New or updated user detected in Intercom (or scheduled sync interval)
- Action: Search Zendesk for a matching user record by email address
- Action: Create or update the Zendesk user with mapped attributes from Intercom, and write back any Zendesk-specific fields to Intercom
Connectors Used: Intercom, Zendesk
Template
Route New Zendesk Tickets by Intercom Customer Segment
When a new Zendesk ticket is created, this template queries Intercom for the submitting customer's segment or subscription data and automatically reassigns the ticket to the appropriate Zendesk group or agent queue.
Steps:
- Trigger: New ticket created in Zendesk
- Action: Look up the ticket requester's email in Intercom to retrieve their plan tier or segment tag
- Action: Update the Zendesk ticket's group assignment or priority based on the returned segment data
Connectors Used: Zendesk, Intercom
Template
Send Intercom Message When Zendesk Ticket is Created via Web Form
Detects new Zendesk tickets submitted through a web form or email channel and immediately sends a personalized Intercom message to the customer acknowledging receipt and providing an estimated response time.
Steps:
- Trigger: New Zendesk ticket created via web form or email
- Action: Retrieve customer details from the Zendesk ticket requester field
- Action: Send a proactive Intercom message to the customer with ticket reference and expected SLA
Connectors Used: Zendesk, Intercom
Template
Aggregate Intercom and Zendesk CSAT Data into a Reporting Dashboard
Collects CSAT survey responses and conversation-close events from both Intercom and Zendesk on a scheduled basis, normalizes the data, and pushes the combined dataset to Google Sheets or a connected BI tool for unified support performance reporting.
Steps:
- Trigger: Scheduled daily or weekly run
- Action: Fetch CSAT scores and volume metrics from Intercom and Zendesk APIs
- Action: Normalize and merge datasets, then write the unified report to Google Sheets or a data warehouse
Connectors Used: Intercom, Zendesk