Zendesk + Zendesk Sell (formerly Base)
Connect Your Support Desk and Sales Pipeline with Zendesk + Zendesk Sell
Stop copying data between your support desk and CRM. tray.ai keeps both in sync so your teams can focus on customers, not busywork.
Why integrate Zendesk and Zendesk Sell (formerly Base)?
Zendesk and Zendesk Sell (formerly Base) handle opposite ends of the customer relationship — one handles support, the other handles sales — but they share the same customers. Despite living in the same ecosystem, the two tools often don't talk to each other, so sales reps chase down ticket history manually and support agents dig through CRM records to find basic account context. Integrating Zendesk with Zendesk Sell on tray.ai closes that gap with real-time data flow between your support and sales teams.
Automate & integrate Zendesk & Zendesk Sell (formerly Base)
Use case
Automatically Create Zendesk Sell Contacts from New Support Tickets
When a new customer submits a support ticket in Zendesk, tray.ai checks whether that user already exists as a contact in Zendesk Sell and creates one if they don't. Your sales team gets a complete contact list without any manual data entry, and reps can immediately see inbound activity from prospective accounts.
Use case
Sync Ticket Status and History to Zendesk Sell Deal Records
Keep your sales team informed by automatically logging Zendesk ticket activity — status changes, priority updates, resolution notes — directly to the associated deal or contact record in Zendesk Sell. Account executives get a current view of open issues that could affect deal progression, without switching tabs or asking colleagues what's going on in the queue.
Use case
Escalate High-Value Support Tickets Based on Deal Size in Zendesk Sell
When a contact linked to a high-value deal submits a support ticket, tray.ai checks the associated deal value in real time and can apply priority tags, assign dedicated agents, or notify account managers immediately. Your most important prospects and customers don't get lost in a standard queue.
Use case
Create or Update Zendesk Sell Leads When Prospects Submit Support Requests
When a prospect who isn't yet in your CRM submits a Zendesk ticket, tray.ai can create a new lead in Zendesk Sell and populate it with contact details and ticket context. No potential customer falls through the cracks, and SDRs get a warm, context-rich lead to follow up on instead of a cold name.
Use case
Notify Sales Reps When a Deal's Contact Submits a New Ticket
When a contact tied to an active Zendesk Sell deal submits a new support ticket, tray.ai can instantly notify the deal owner via email, Slack, or an in-app note in Zendesk Sell. Reps stay aware of customer experience issues without monitoring the support queue, and can reach out proactively to acknowledge the problem.
Use case
Automatically Close or Update Zendesk Sell Deals Based on Ticket Outcomes
When a support ticket is resolved — especially one flagged as a deal-blocking issue — tray.ai can update the corresponding deal stage in Zendesk Sell, moving it forward or marking it closed-lost based on the outcome and your custom logic. CRM stages reflect what's actually happening with the customer, without a rep having to update anything manually.
Use case
Sync Zendesk Sell Account Updates Back to Zendesk Organization Records
When account details like company name, industry, or contact information change in Zendesk Sell, tray.ai reflects those changes in the corresponding Zendesk organization or user record. Both platforms stay accurate without anyone entering data twice, and support agents always have current account context when handling tickets.
Get started with Zendesk & Zendesk Sell (formerly Base) integration today
Zendesk & Zendesk Sell (formerly Base) Challenges
What challenges are there when working with Zendesk & Zendesk Sell (formerly Base) and how will using Tray.ai help?
Challenge
Matching Records Across Two Systems Without a Shared Primary Key
Zendesk and Zendesk Sell use separate internal ID systems, so a ticket requester in Zendesk won't directly map to a contact or lead in Zendesk Sell without fuzzy matching logic based on email or company name. Mismatches mean duplicate records or missed associations.
How Tray.ai Can Help:
tray.ai's data mapping and conditional logic let you define multi-field matching rules — checking email, phone, and company name in sequence — before creating or updating any record. You can also build deduplication workflows that consolidate near-matches and flag ambiguous cases for manual review.
Challenge
Handling Bidirectional Sync Without Triggering Infinite Loops
When both systems need to stay in sync, a change in one can trigger an update in the other, which triggers another event back, and suddenly you have a loop of endless API calls and potential data corruption.
How Tray.ai Can Help:
tray.ai lets you build loop prevention logic using timestamp comparisons, custom field flags, or source-of-change metadata. Workflows can detect whether an update originated from the integration itself and skip processing, stopping runaway sync cycles before they start.
Challenge
Keeping Contact and Account Data Consistent at Scale
As your customer base grows, keeping contact details, company names, and account metadata synchronized across both platforms manually becomes increasingly error-prone. The result is stale data, misrouted tickets, and sales reps missing account context they should have had.
How Tray.ai Can Help:
tray.ai supports high-volume, event-driven workflows that respond to data changes in real time or on a scheduled batch basis. You can configure field-level sync rules that define which system owns each data point, so both platforms stay accurate without manual reconciliation.
Challenge
Translating Different Status and Stage Taxonomies Between Systems
Zendesk uses ticket statuses like New, Open, Pending, and Solved. Zendesk Sell uses deal stages and lead statuses built around a sales pipeline. Mapping these two systems meaningfully requires custom logic that standard native sync tools can't handle.
How Tray.ai Can Help:
tray.ai's workflow builder lets you create custom mapping tables and conditional branches that translate Zendesk ticket statuses into Zendesk Sell stage transitions. A ticket moving to Solved can advance a deal stage; a ticket reopening can trigger a deal flag or alert — all configured with no-code logic blocks.
Challenge
Managing API Rate Limits During High-Volume Sync Events
Both Zendesk and Zendesk Sell enforce API rate limits that can become a bottleneck during bulk syncs, initial data migrations, or high-traffic periods. Workflows that don't account for this can fail silently or drop records.
How Tray.ai Can Help:
tray.ai has built-in rate limit handling with automatic retry logic, exponential backoff, and error alerting so workflows manage API quotas without losing data. You can also schedule bulk operations during off-peak hours and use tray.ai's queueing to throttle requests within safe limits.
Start using our pre-built Zendesk & Zendesk Sell (formerly Base) templates today
Start from scratch or use one of our pre-built Zendesk & Zendesk Sell (formerly Base) templates to quickly solve your most common use cases.
Zendesk & Zendesk Sell (formerly Base) Templates
Find pre-built Zendesk & Zendesk Sell (formerly Base) solutions for common use cases
Template
New Zendesk Ticket → Create or Match Contact in Zendesk Sell
Every time a new ticket is created in Zendesk, this template searches for a matching contact in Zendesk Sell. If there's no match, it creates a new contact automatically with ticket metadata attached, so your CRM stays complete without manual upkeep.
Steps:
- Trigger: New ticket created in Zendesk
- Lookup: Search Zendesk Sell for a contact matching the ticket requester's email
- Branch: If contact exists, update record; if not, create a new Zendesk Sell contact with ticket details
Connectors Used: Zendesk, Zendesk Sell (formerly Base)
Template
Zendesk Ticket Priority Change → Update Zendesk Sell Deal Note
When a support ticket's priority is escalated in Zendesk, this template adds a timestamped note to the related deal in Zendesk Sell, so the account owner knows a customer's support status has changed.
Steps:
- Trigger: Ticket priority updated to High or Urgent in Zendesk
- Lookup: Find the associated deal or contact in Zendesk Sell by requester email
- Action: Create a note on the Zendesk Sell deal record with ticket ID, priority level, and summary
Connectors Used: Zendesk, Zendesk Sell (formerly Base)
Template
New Zendesk Sell Deal Won → Create VIP Organization Tag in Zendesk
When a deal is marked Won in Zendesk Sell, this template applies a VIP or priority tag to the associated Zendesk organization so support agents immediately know they're working with a paying customer and can route tickets accordingly.
Steps:
- Trigger: Deal stage updated to Won in Zendesk Sell
- Lookup: Find or create the matching organization in Zendesk using the deal's account name or email domain
- Action: Apply a custom VIP or priority tag to the Zendesk organization record
Connectors Used: Zendesk Sell (formerly Base), Zendesk
Template
Resolved Zendesk Ticket → Advance Deal Stage in Zendesk Sell
When a deal-blocking support ticket is resolved in Zendesk, this template moves the associated deal to the next stage in Zendesk Sell, keeping your pipeline accurate and triggering timely sales follow-up.
Steps:
- Trigger: Ticket with a specific tag (e.g., 'deal-blocker') is marked Solved in Zendesk
- Lookup: Find the associated deal in Zendesk Sell by contact email or custom field mapping
- Action: Update the deal stage to the next defined stage and add a resolution note
Connectors Used: Zendesk, Zendesk Sell (formerly Base)
Template
New Zendesk Sell Lead → Auto-Create Zendesk User Record
When a new lead is added to Zendesk Sell, this template creates a matching user record in Zendesk so any future support requests from that lead are immediately recognized and given the right context.
Steps:
- Trigger: New lead created in Zendesk Sell
- Check: Verify no existing Zendesk user with matching email address exists
- Action: Create a new Zendesk user with lead name, email, company, and custom tags from the Sell record
Connectors Used: Zendesk Sell (formerly Base), Zendesk
Template
Daily Ticket Summary Report Synced to Zendesk Sell Account Records
On a daily schedule, this template pulls open and resolved ticket counts per account from Zendesk and writes a support health summary to each matching account record in Zendesk Sell, so account managers start each day knowing where their customers stand.
Steps:
- Trigger: Scheduled daily run at a configured time
- Query: Pull all tickets grouped by organization from Zendesk for the past 24 hours
- Action: Loop through accounts and post a formatted support summary note to each matching Zendesk Sell account record
Connectors Used: Zendesk, Zendesk Sell (formerly Base)