CRM integration guide
Zendesk Sell + UbiGrowth workflows
Zendesk Sell is the sales CRM in the Zendesk suite, where deal and sales activity data sits next to support conversations. This guide covers the records that matter, how the connection should be scoped, and what the first bounded workflow should be.
Introduction
Make Zendesk Sell part of the workflow, not another silo.
Validate connector availability for your workspace
This guide covers how a team designs a CRM workflow around Zendesk Sell with UbiGrowth: which records stay authoritative, how the connection should be scoped, what the first bounded workflow should be, and how to tell whether it worked.
The records that matter are Lead, Contact, Deal, Task, Appointment, and Note. Zendesk Sell and Zendesk Support share a brand but not a customer record. The same person is a Sell Contact and a Support User with separate ids, so the joined view has to be built rather than assumed.
Zendesk Sell is not currently on UbiVibe's verified connector list. This page is an implementation design reference: use it to specify the workflow, then validate whether the connection is available and correctly scoped for your workspace before you make it a dependency. The verified UbiVibe connections today are Salesforce, HubSpot, Gmail, Google Drive, Slack, and GitHub.
Grow is the usual destination for this connection, because the value shows up as outreach, reply handling, scheduling, and pipeline execution against the connected records.
Why teams evaluate this connection
Integrations create value when they remove operating friction.
The first design decision is not which API endpoint to call; it is which system owns the record, what event should trigger work, who owns the exception path, and what successful completion means.
The recurring failure with a Zendesk Sell integration is not connectivity. It is that the CRM ends up holding a record of what someone remembered to log, while the work itself happened in an inbox, a call, a spreadsheet, and a separate AI tool that never saw the account.
When that gap exists, everything built on top of it inherits it. Forecasts describe logged activity rather than real activity, outreach is written without the reply history that would make it relevant, and the team spends its day reconciling systems instead of working accounts.
You're likely here because
- Pipeline data is only as current as the last time someone logged activity
- Outreach is generated without the account history that would ground it
- The same account context is rebuilt in several tools each day
Record model
What a Zendesk Sell integration actually reads and writes.
Integration design starts from the objects the system really exposes, not from a generic connector diagram. These are Zendesk Sell's.
Identity and matching
Zendesk Sell and Zendesk Support share a brand but not a customer record. The same person is a Sell Contact and a Support User with separate ids, so the joined view has to be built rather than assumed.
Start here
Join open Deals to Support tickets from the same company and surface the deals where an unresolved support issue is the actual blocker.
What this will not do
It will not give support agents pipeline context automatically. That join is the work, not a side effect of both products being Zendesk.
The constraint to plan around
Sell's API and Support's API authenticate separately with different tokens and rate limits; a single Zendesk credential does not reach both.
Build notes
What you actually have to reason about in Zendesk Sell.
The fields that carry meaning, how the connection authenticates, and whether the event surface can be trusted. This is the part that decides whether the integration works in month three.
| Field | Why it matters |
|---|---|
| stage_id | deal progression, and unrelated to any Zendesk Support status despite the shared brand |
| owner_id | a Sell user id, which is not the same identifier as the Support agent id for the same person |
| contact_id | the Sell-side person, distinct from the Support User with no automatic link between them |
| value / currency | deal amount, where multi-currency accounts need the exchange context to aggregate |
| last_stage_change_at | the field that makes stalling visible, which the stage alone does not |
Authentication
OAuth access token specific to Sell, entirely separate from a Support API token. Two Zendesk products means two credentials, two rate limits, and two permission models, and the shared brand causes teams to assume otherwise.
Events and delivery
Sell exposes a firehose-style change feed rather than configurable webhooks, so consumption is a stream you keep position in rather than callbacks you receive.
Workflow
How the Zendesk Sell workflow runs.
The operating sequence, from reading the source system through to the result landing back where it belongs.
Step 01
Read the pipeline as it stands
The workflow starts from live Zendesk Sell accounts, contacts, and opportunities rather than an export, so prioritization reflects today's pipeline.
Step 02
Assemble the account context
Reply history, documents, and prior activity are brought together so the next action is grounded in what actually happened with the account.
Step 03
Decide the next action
ARIA proposes the specific next step for the account, with the supporting context attached, instead of producing a message with no stated reason.
Step 04
Execute through Grow
Outreach, reply handling, and scheduling run against the same record, staged for review while the motion is being proven.
Design decisions
The CRM decisions this connection forces.
Each of these has to be settled before the Zendesk Sell workflow is allowed to write anything.
Step 01
Resolve the account identity
Decide how a person and a company are matched between Zendesk Sell and the rest of the stack before any write happens. Most CRM integration damage is duplicate records created by a weak match rule.
Step 02
Keep execution attached to the opportunity
Outreach, replies, meetings, and stage changes should resolve back to the same opportunity, so the CRM reflects what actually happened rather than a parallel activity log.
Implementation path
How to implement the Zendesk Sell workflow.
- 01
Decide which fields Zendesk Sell owns and which the workflow may write, and write that decision down before enabling anything.
- 02
Define the identity match rule for contacts and companies, including what happens on an ambiguous match.
- 03
Start read-only. Prove that the workflow reads the right records before it is allowed to change any of them.
- 04
Once support-blocked deals are visible, invert it: flag support tickets from accounts with an open deal so the support queue reflects commercial context.
Governance
Controls that matter.
Control 01
CRM write scopes are limited to the specific objects the workflow needs, never blanket admin access.
Control 02
Duplicate creation is treated as a defect, not an acceptable side effect of syncing.
Control 03
Stage changes and closed-won updates stay under human control; automation prepares them rather than deciding them.
Failure modes
How a Zendesk Sell integration breaks in production.
Not generic integration advice. These follow from how this system actually behaves, which is why they look nothing like the list on the next guide over.
Symptom 01
A Zendesk credential works for Support and fails for Sell.
Cause
They are separate products with separate authentication.
Fix
Provision and store both credentials, and expect two rate limits.
Symptom 02
The joined customer view has gaps.
Cause
Sell Contacts and Support Users are separate objects with no automatic link.
Fix
Build the join on email and company domain deliberately, and report the unmatched rate rather than hiding it.
Symptom 03
The change feed position is lost and the sync restarts from the beginning.
Cause
The firehose cursor was not persisted.
Fix
Persist the cursor transactionally with the work it represents.
What changes at scale
The firehose model scales better than polling for high-change accounts, but requires durable cursor management. That is the design decision to make early rather than retrofit.
Examples
What a working Zendesk Sell workflow looks like.
Bounded scenarios rather than a feature list. Each one can be verified against work the team already does.
Deal workflows
With Zendesk Sell connected, ARIA works from live account, contact, and opportunity records instead of an export, so prioritization reflects the pipeline as it stands today.
Grounded outbound
Grow drafts outreach against the account history already in Zendesk Sell, so the message references what actually happened with the account rather than a generic template.
Limitations and considerations
What to validate before you depend on this.
- Sell's API and Support's API authenticate separately with different tokens and rate limits; a single Zendesk credential does not reach both.
- Cross-writing between Sell and Support on the assumption of a shared customer record puts data on the wrong object. Nothing errors, because both objects accept it.
- When Support is already in place and Sell is being adopted only for adjacency. The join has to be built either way, so the shared vendor buys less than it appears to.
- If Zendesk Sell data is incomplete, the workflow inherits that gap. Connected context is not automatically accurate context.
- Custom objects, custom fields, and heavily-customized permission models change what an integration can safely do; validate them against your own instance rather than the vendor default.
FAQ
Zendesk Sell integration questions.
What records does a Zendesk Sell integration actually work with?
The primary records are Lead, Contact, Deal, Task, Appointment, and Note. Zendesk Sell and Zendesk Support share a brand but not a customer record. The same person is a Sell Contact and a Support User with separate ids, so the joined view has to be built rather than assumed.
What should the first Zendesk Sell workflow be?
Join open Deals to Support tickets from the same company and surface the deals where an unresolved support issue is the actual blocker.
What will a Zendesk Sell integration not do?
It will not give support agents pipeline context automatically. That join is the work, not a side effect of both products being Zendesk.
What is the main constraint to plan around?
Sell's API and Support's API authenticate separately with different tokens and rate limits; a single Zendesk credential does not reach both.
What changes about a Zendesk Sell integration at scale?
The firehose model scales better than polling for high-change accounts, but requires durable cursor management. That is the design decision to make early rather than retrofit.
How does authentication work for Zendesk Sell?
OAuth access token specific to Sell, entirely separate from a Support API token. Two Zendesk products means two credentials, two rate limits, and two permission models, and the shared brand causes teams to assume otherwise.
Does Zendesk Sell support webhooks, and can they be trusted?
Sell exposes a firehose-style change feed rather than configurable webhooks, so consumption is a stream you keep position in rather than callbacks you receive.
What is the risk of writing to Zendesk Sell?
Cross-writing between Sell and Support on the assumption of a shared customer record puts data on the wrong object. Nothing errors, because both objects accept it.
When is connecting Zendesk Sell the wrong call?
When Support is already in place and Sell is being adopted only for adjacency. The join has to be built either way, so the shared vendor buys less than it appears to.
What should a Zendesk Sell integration automate first?
Start with one bounded workflow that removes a measurable handoff, duplicate-entry step, reporting delay, or follow-up gap. Expand only after the first workflow is reliable.
Does UbiGrowth require Zendesk Sell to be replaced?
No. The operating model is designed around connecting to systems that should remain authoritative and building workflows around them rather than forcing a wholesale replacement.
Is connector availability identical for every workspace?
No. Availability can depend on provider configuration, authentication, scopes, workspace setup, and deployment state. Validate the required connection before treating it as an operational dependency.
Will this create duplicate records in Zendesk Sell?
Only if the identity match rule is weak. Define how people and companies are matched, and how ambiguous matches are handled, before enabling any write path.
Does Zendesk Sell stay the system of record?
Yes. The design assumption is that Zendesk Sell remains authoritative for the objects it owns and the workflow builds around it rather than replacing it.
Can pipeline stages be updated automatically?
Stage progression should stay under human control. Automation can prepare and propose the update, but deciding that a deal moved is a judgment call.
How this access is governed
What ARIA is allowed to do in Zendesk Sell, and who decides.
Connecting Zendesk Sell is a permission decision, not just a setup step. These are the controls that decide what ARIA can reach, what it can change, what gets recorded, and how you take the access back.
Required permissions
ARIA works through the scopes the connection was granted, and no others. Authorization happens at the provider, so the permissions being requested are shown by the system itself before anything is connected.
What it can reach
Reachable systems are the intersection of what your organization approved in the connector registry and what the requesting identity is permitted to use. Identity resolves before execution, not after.
What it can do
Actions run through explicit execution paths with state, spend, and failure boundaries — a bounded worker path rather than an open-ended agent loop with a credential.
Credential handling
Credentials live in the governed connection layer and are resolved through canonical connection identity. They are not pasted into individual workflows, prompts, or generated artifacts.
Action logging
Execution carries state and traces: what triggered the work, which connection it used, and what came back — including an explicit failure when something did not run.
Approval and revocation
Consequential actions can be made to require a person to approve them. Access can be changed or revoked at the connection, and ARIA loses that reach without unpicking the work already completed.
Start with ARIA
Ask ARIA to run this integration.
Describe the outcome you need across this system. ARIA works out the scopes, data, and actions the job requires, and operates inside the access you grant — which you can change or revoke.
- ARIA acts only through the systems and permissions you connect.
- Connections use scoped credentials you can change or revoke.
- Actions are recorded, and consequential ones can require approval.
Start here
Turn the integration into a working business outcome.
Start with ARIA to describe the outcome, then continue into the product path that fits the workflow. Connector availability and required scopes should be validated for the specific workspace before production use.