Zendesk Sell (formerly Base) + HubSpot
Connect Zendesk Sell and HubSpot to Unify Your Sales and Marketing Engine
Automate lead handoffs, sync contact data, and get sales and marketing working from the same playbook — no manual effort required.
Why integrate Zendesk Sell (formerly Base) and HubSpot?
Zendesk Sell and HubSpot are two workhorses in the modern revenue stack. Zendesk Sell handles pipeline management and sales activity tracking; HubSpot runs inbound marketing, lead nurturing, and CRM workflows. Together, they bridge the gap between marketing-qualified leads and active sales opportunities. Integrating the two cuts out data silos, speeds up lead response times, and gives both teams a shared view of the customer journey.
Automate & integrate Zendesk Sell (formerly Base) & HubSpot
Use case
Automated Lead Handoff from HubSpot to Zendesk Sell
When a lead hits a qualification threshold in HubSpot — a specific lead score, form submission, or lifecycle stage change — tray.ai automatically creates a new lead or contact in Zendesk Sell and routes it to the right sales rep. No more CSV exports or delayed follow-ups. Reps get enriched leads with full HubSpot engagement context already attached.
Use case
Sync Deal Stage Updates Back to HubSpot for Revenue Attribution
As deals move through stages in Zendesk Sell, tray.ai mirrors those changes as deal or lifecycle updates in HubSpot, giving marketing accurate, real-time pipeline visibility. This powers closed-loop reporting so marketers can tie specific campaigns, content, and channels to actual revenue. Marketing ops gets the attribution data they need to double down on what's working.
Use case
Bidirectional Contact and Company Record Synchronization
Any new or updated contact and company record in either Zendesk Sell or HubSpot is automatically reflected in the other platform, keeping both systems consistent without manual reconciliation. Field-level mapping keeps properties like phone numbers, job titles, company size, and custom fields accurate across both platforms. De-duplication logic prevents duplicate records from cluttering either system.
Use case
Trigger HubSpot Nurture Sequences from Zendesk Sell Deal Outcomes
When a deal is marked as lost in Zendesk Sell, tray.ai can automatically enroll the associated contact into a re-engagement or nurture workflow in HubSpot, keeping the relationship alive for future opportunities. Closed-won deals can trigger onboarding email sequences, customer success workflows, or upsell campaigns in HubSpot. The customer journey keeps moving without anyone having to remember to push a button.
Use case
Sales Activity Logging for Marketing Intelligence
Call logs, emails, and meeting notes recorded in Zendesk Sell can be synced to HubSpot contact timelines, giving marketing teams a complete picture of sales touchpoints alongside marketing interactions. That fuller activity history helps marketing understand which content and campaigns actually influence sales conversations — and supports compliance and record-keeping across both systems.
Use case
New HubSpot Company Creation from Zendesk Sell Accounts
When a new account is created in Zendesk Sell — whether from an inbound inquiry or outbound prospecting — tray.ai instantly creates or updates the corresponding company record in HubSpot. Account-based marketing lists, company workflows, and segment targeting in HubSpot always reflect the latest accounts in the sales pipeline. Account executives and marketers stay on the same page about target accounts.
Use case
Zendesk Sell Lead Enrichment Using HubSpot Contact Intelligence
When a new lead is created in Zendesk Sell, tray.ai queries HubSpot for existing contact data, engagement scores, and historical campaign interactions, then enriches the Zendesk Sell record with that intelligence. Reps immediately see which emails the lead has opened, which pages they've visited, and which offers they've engaged with — without ever leaving Zendesk Sell. That context makes a real difference on the first call.
Get started with Zendesk Sell (formerly Base) & HubSpot integration today
Zendesk Sell (formerly Base) & HubSpot Challenges
What challenges are there when working with Zendesk Sell (formerly Base) & HubSpot and how will using Tray.ai help?
Challenge
Preventing Infinite Sync Loops Between Two Active CRMs
When both Zendesk Sell and HubSpot are live systems that sales and marketing teams update constantly, a bidirectional sync can easily trigger endless loops where an update in one system triggers an update in the other, which triggers another update back — corrupting data and hammering both APIs.
How Tray.ai Can Help:
tray.ai handles loop prevention natively by stamping synced records with a cross-system ID and last-sync timestamp during each workflow run. Conditional logic checks whether an incoming change originated from the tray.ai sync itself before triggering an outbound update, breaking the loop at the workflow level without any custom code.
Challenge
Mapping Mismatched Pipeline Stages and Lifecycle Stages
Zendesk Sell has its own deal stage terminology and pipeline structure; HubSpot has its own deal stages, lifecycle stages, and lead statuses. They rarely map one-to-one out of the box. Without careful mapping, synced records land in the wrong stages and create reporting errors that confuse both teams.
How Tray.ai Can Help:
tray.ai's workflow builder includes a configurable lookup table and conditional branching so operations teams can define exact stage mappings between Zendesk Sell and HubSpot. These mappings can be updated without engineering involvement, and separate mapping logic can be applied for different pipelines or business units as the company scales.
Challenge
Deduplicating Contacts That Exist in Both Systems Under Different Records
Over time, contacts build up in both Zendesk Sell and HubSpot through different channels — a sales rep manually enters a lead in Zendesk Sell while the same person filled out a HubSpot form months earlier. Without deduplication logic, the sync creates redundant records and splits engagement history across duplicates.
How Tray.ai Can Help:
tray.ai workflows run a multi-field deduplication check — matching on email address as the primary key, with fallback logic using name and company domain — before creating any new record. When a potential duplicate is detected, the workflow updates the existing record rather than creating a new one, and can optionally flag the match for human review via a Slack notification or task creation.
Challenge
Handling API Rate Limits During Large Historical Data Syncs
Initial syncs between Zendesk Sell and HubSpot often involve thousands of contacts, companies, and deals that need to be migrated or reconciled. Both APIs have rate limits that, when exceeded during bulk operations, cause failed requests, incomplete syncs, and data inconsistencies that are hard to diagnose and fix after the fact.
How Tray.ai Can Help:
tray.ai manages API rate limiting with built-in retry logic, exponential backoff, and request throttling at the connector level. For large historical syncs, workflows can be configured to process records in batches with configurable delays between them, so the migration completes fully without hitting rate limit errors on either API.
Challenge
Keeping Custom Fields and Properties Aligned Across Both Platforms
Both Zendesk Sell and HubSpot let teams create custom fields and properties, and over time each platform accumulates unique fields the other doesn't have. Data gets lost in translation during sync, or ends up stored in non-obvious fields as a workaround.
How Tray.ai Can Help:
tray.ai has a flexible field mapping interface where custom fields in Zendesk Sell can be precisely mapped to custom properties in HubSpot and vice versa. Transformation functions let data be reformatted, concatenated, or split to fit the target system's schema. When new custom fields are added to either platform, operations teams can update the mapping directly in the workflow editor — no code changes required.
Start using our pre-built Zendesk Sell (formerly Base) & HubSpot templates today
Start from scratch or use one of our pre-built Zendesk Sell (formerly Base) & HubSpot templates to quickly solve your most common use cases.
Zendesk Sell (formerly Base) & HubSpot Templates
Find pre-built Zendesk Sell (formerly Base) & HubSpot solutions for common use cases
Template
HubSpot MQL to Zendesk Sell Lead — Automated Handoff
Monitors HubSpot for contacts that reach marketing-qualified lead status and automatically creates a corresponding lead record in Zendesk Sell, complete with mapped contact fields, lead source, and HubSpot engagement score, then assigns it to the appropriate sales rep based on routing rules.
Steps:
- Trigger when a HubSpot contact's lifecycle stage changes to Marketing Qualified Lead or lead score crosses a defined threshold
- Map and transform HubSpot contact fields including name, email, company, lead score, and campaign source to Zendesk Sell lead fields
- Check for existing records in Zendesk Sell to prevent duplicate lead creation using email as the unique identifier
- Create or update the lead record in Zendesk Sell and assign it to the correct sales rep based on territory or round-robin logic
- Log the handoff event back to HubSpot as a contact activity to maintain a complete audit trail
Connectors Used: HubSpot, Zendesk Sell (formerly Base)
Template
Zendesk Sell Deal Stage Sync to HubSpot Deal Pipeline
Listens for deal stage changes in Zendesk Sell and mirrors those updates to the corresponding HubSpot deal record, keeping both CRM pipelines aligned and enabling accurate closed-loop marketing attribution reporting.
Steps:
- Trigger when a deal stage is updated in Zendesk Sell via webhook or polling
- Look up the associated HubSpot deal using the linked contact email or a shared custom ID field
- Map the Zendesk Sell deal stage to the equivalent HubSpot deal stage using a configurable stage mapping table
- Update the HubSpot deal record with the new stage, close date, and deal value from Zendesk Sell
- Update the associated HubSpot contact lifecycle stage if the deal is marked closed-won or closed-lost
Connectors Used: Zendesk Sell (formerly Base), HubSpot
Template
Bidirectional Contact Sync — Zendesk Sell and HubSpot
Continuously synchronizes contact records between Zendesk Sell and HubSpot in both directions, resolving conflicts with a configurable last-updated-wins or source-of-truth logic, and preventing duplicate records through email-based deduplication.
Steps:
- Trigger on contact create or update events in either Zendesk Sell or HubSpot using webhooks
- Perform a deduplication check in the target system using email address as the primary key
- Apply field mapping rules to translate platform-specific properties into the target system's schema
- Create a new record or update the existing record in the target system with the transformed data
- Stamp both records with a shared sync timestamp and cross-system ID to prevent sync loop conflicts
Connectors Used: Zendesk Sell (formerly Base), HubSpot
Template
Closed-Lost Deal in Zendesk Sell Triggers HubSpot Re-engagement Workflow
Detects when a deal is marked closed-lost in Zendesk Sell and automatically enrolls the associated contact in a HubSpot re-engagement email workflow, while also updating the contact's lifecycle stage and adding a relevant tag for segmentation.
Steps:
- Trigger when a deal status changes to lost in Zendesk Sell
- Retrieve the associated contact record and loss reason from Zendesk Sell
- Look up the corresponding contact in HubSpot using the contact's email address
- Update the HubSpot contact lifecycle stage and add a custom property indicating the deal was lost and the reason
- Enroll the contact in the appropriate HubSpot re-engagement workflow based on the deal's industry, value, or loss reason tag
Connectors Used: Zendesk Sell (formerly Base), HubSpot
Template
New Zendesk Sell Account Synced to HubSpot Company Record
Automatically creates or updates a HubSpot company record whenever a new account is added in Zendesk Sell, so account-based marketing lists and company workflows in HubSpot always reflect the full book of business tracked by sales.
Steps:
- Trigger when a new account is created or significantly updated in Zendesk Sell
- Search HubSpot for an existing company record using the account domain or company name
- Map Zendesk Sell account fields such as industry, employee count, and annual revenue to HubSpot company properties
- Create a new HubSpot company or update the existing record with the latest data from Zendesk Sell
- Associate the HubSpot company with existing contact records that share the same email domain
Connectors Used: Zendesk Sell (formerly Base), HubSpot
Template
HubSpot Form Submission Creates Zendesk Sell Lead with Engagement Context
When a prospect submits a high-intent form in HubSpot — such as a demo request or pricing inquiry — tray.ai instantly creates a prioritized lead in Zendesk Sell enriched with the form data, page history, and HubSpot lead score, then sends a Slack or email alert to the assigned rep.
Steps:
- Trigger when a specific HubSpot form is submitted or a high-intent conversion event occurs
- Retrieve the full HubSpot contact record including engagement history, lead score, and recent page views
- Check Zendesk Sell for an existing lead or contact record to avoid duplication
- Create or update the Zendesk Sell lead with all relevant HubSpot fields and append a note summarizing the contact's engagement history
- Send an instant notification to the assigned sales rep via email or Slack with lead details and a direct link to the Zendesk Sell record
Connectors Used: HubSpot, Zendesk Sell (formerly Base)