CRM & Sales · Integration
Zendesk Sell
Add Zendesk Sell to your product for your customers, and give your AI agents governed access to it.
Zendesk Sell is the sales CRM rather than the help desk, and the two are separate products reached separately, so connecting one tells you nothing about the other. Sell is organised around the lead that becomes a contact and a deal, the pipeline stages that deal moves through, and the notes, tasks and calls logged against all three. An embedded Sell integration creates and updates leads, contacts, deals and their custom fields, moves a deal between stages, logs activity, and reads the pipeline so your product can show where revenue actually sits. Two practical details are worth knowing. Conversion turns a lead into a contact and optionally a deal in one operation, so it is not the same thing as an update. And upsert lets you match on an external id you own, which is what keeps a repeated sync from breeding duplicates. fastn holds each account's credentials per tenant.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Zendesk Sell account so deals your product creates land in the pipeline their reps work.
Create or upsert leads and contacts matched on an external id, so a repeated sync updates rather than duplicates.
Move a deal to its next stage when your product sees the event that justifies moving it.
Log calls, notes and tasks against the record, so activity that happened outside Sell still shows up in its history.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent summarises what has happened on a deal by reading its notes, calls and stage history.
An agent creates or updates a deal within scoped permissions, with the fields it set recorded.
An agent lists the deals in one pipeline that nothing has been logged against for a fortnight.
Example prompt
Which deals in this pipeline have not moved in two weeks, and what was logged on them last?
Set up Zendesk Sell in 4 steps
- 01Enable the Zendesk Sell connector in your fastn dashboard.
- 02Have each customer authorise Sell itself, separately from any Zendesk help desk account they also connect.
- 03Map that account's pipelines, stages and custom fields, and choose the external id your upserts match on.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Zendesk Sell integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Zendesk Sell integration without building it. Your customers connect their own Zendesk Sell account inside your product and work their accounts, contacts and opportunities there, with no per-customer code on your side.
- Handle the part that actually costs time: every CRM instance is customised, so standard objects are never the whole story. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Zendesk Sell update is not your on-call problem.
- One integration serves your product and your agents. The same governed Zendesk Sell connection powers in-product features and gives AI agents scoped, audited access, so you keep customer records aligned between your product and the CRM each customer already runs without wiring it twice.
Used by these teams
Compare with
Pipedrive
HubSpotWorks well with
ZendeskOften used alongside
Tools the same teams tend to run next to Zendesk Sell, across other categories.
Slack
Mailchimp
Marketo
Google AdsZendesk Sell integration FAQ
How do I add a Zendesk Sell integration to my product?
Enable the Zendesk Sell connector in your fastn dashboard, then let each customer authenticate their own Zendesk Sell account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Zendesk Sell client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Zendesk Sell account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Zendesk Sell account and only ever sees their own accounts, contacts and opportunities. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Zendesk Sell integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent summarises what has happened on a deal by reading its notes, calls and stage history.
Who maintains the Zendesk Sell integration?
fastn does. When Zendesk Sell changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Does the Zendesk Sell integration support custom fields and custom objects?
Yes. CRM instances are heavily customised, so field and object mapping is configuration rather than code. Each customer maps their own fields during setup, which means onboarding a customer with an unusual Zendesk Sell schema does not require a deploy on your side.
Can records sync both ways?
Yes. You can read from Zendesk Sell, write back to it, and react to changes through triggers, so a record updated in your product and a record updated in Zendesk Sell do not drift apart.
What can I build with the Zendesk Sell integration?
A common starting point: let each customer connect their own Zendesk Sell account so deals your product creates land in the pipeline their reps work. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Zendesk Sell integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Zendesk Sell does not change your per-connector cost. You can start free with 3 connected accounts.
Add Zendesk Sell to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.