Source connector

Zendesk Sell connector

Zendesk Sell integration for databases, warehouses and BI tools

Sales CRM for lead and deal tracking in Zendesk ecosystems. Datrise captures Zendesk Sell entities such as leads, deals, activities, and Zendesk-aligned sales operations, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Zendesk Sell (Sales CRM) Core API, plus the Sync and Firehose APIs authenticates with OAuth 2.0, incremental runs key on Sync API session/queue (event_type + revision), not a plain updated_at field on Core API resources, and Zendesk Sell caps calls at Up to 36,000 requests/hour (roughly 10 requests/second per token); exceeding it returns HTTP 429.

Of the 4 objects, 3 sync as upserts keyed on the primary key and 1 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `zendesk_sell_leads`) with a schema derived from the Zendesk Sell API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the Zendesk Sell pipeline page, and join the waitlist to get the Zendesk Sell connector (CRM) with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Zendesk Sell data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
leads	zendesk_sell_leads	Upsert by primary key, incremental on updated-at
deals	zendesk_sell_deals	Upsert by primary key, incremental on updated-at
activities	zendesk_sell_activities	Append-only, incremental by timestamp
Zendesk-aligned sales operations	zendesk_sell_zendesk_aligned_sales_operations	Upsert by primary key, incremental on updated-at

Zendesk Sell API: setup facts for the connector

Verified against the vendor documentation on 2026-09-02. Unknown values are left blank rather than guessed.

API	Zendesk Sell (Sales CRM) Core API, plus the Sync and Firehose APIs
Authentication	OAuth 2.0 — OAuth 2.0 access tokens are shared across Zendesk APIs; the base endpoint is still `https://api.getbase.com`, a holdover from Sell's original Base CRM branding.
Pagination	page — Core API list/search endpoints use `page`/`per_page`-style pagination with sorting; the separate Sync API instead uses a stateful session/queue model (`/v2/sync/start` -> fetch queue pages -> acknowledge), not client-driven offsets.
Rate limit	Up to 36,000 requests/hour (roughly 10 requests/second per token); exceeding it returns HTTP 429.
Incremental cursor	Sync API session/queue (event_type + revision), not a plain updated_at field on Core API resources — The Sync API is Sell's purpose-built incremental mechanism: after `POST /v2/sync/start`, a client fetches queued change items (each carrying `event_type`, `ack_key`, `revision`) and acknowledges them, rather than polling Core API list endpoints with a timestamp filter.
Webhooks	Yes — Firehose API (near real-time stream of change events, functioning like a webhook/CDC feed)
Bulk export	No
Deletes detectable	Yes — Sync API items for deleted resources include only the resource `id` (no other fields) and are documented as an explicit instruction to perform a local delete.

Official API reference

What bites when replicating Zendesk Sell

The Sync API requires an `X-Basecrm-Device-UUID` header that must stay identical across every session for the same integration instance; changing it makes Sell treat the caller as a brand-new device and resend the entire dataset from scratch.
The Sync API only guarantees eventual consistency, not ordering, so a connector cannot assume change events arrive in the sequence they occurred and must reconcile by resource state/revision rather than by event order.
Deleted-resource sync items omit every field except `id`; a connector that expects to read a deleted record's last-known field values from the sync feed itself will get nothing and must already have those values cached locally.
The published 36,000 requests/hour ceiling (about 10/second per token) is a single unified budget shared across the Core, Sync, Search, and Firehose surfaces, not a separate allowance per API, so heavy Sync polling can starve concurrent Core API calls on the same token.

Compare this against every other documented API

Popular destinations for Zendesk Sell

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

Zendesk Sell connector FAQ

What Zendesk Sell data does the connector extract?: 4 objects: leads, deals, activities and Zendesk-aligned sales operations. Each lands in its own table with types preserved; history-style objects (1: activities) load as append-only streams.
Is the Zendesk Sell integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load Zendesk Sell data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Zendesk Sell → destination pair has its own page with the object-to-table mapping.

Related CRM sources

Other sources in the same category, each with its own connector page.

Early access

Launch your Zendesk Sell pipeline with guided onboarding

Join the waitlist to get priority access for Zendesk Sell integrations with guided setup, schema-aware mapping, and production-grade incremental sync.