Source connector

Zendesk connector

Zendesk integration for databases, warehouses and BI tools

Customer support suite with tickets and knowledge base. Datrise captures Zendesk entities such as tickets, users, organizations, macros, and satisfaction ratings, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Zendesk Support API v2 authenticates with OAuth 2.0, API key, HTTP Basic, incremental runs key on cursor (or start_time on the time-based endpoint), and Zendesk caps calls at 200-2,500 requests/minute to the Support/Help Center API depending on plan (Team 200, Professional 400, Enterprise 700, High Volume add-on 2,500 per minute).

Of the 5 objects, 5 sync as upserts keyed on the primary key and 0 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_tickets`) with a schema derived from the Zendesk 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 pipeline page, and join the waitlist to get the Zendesk connector with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Zendesk 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
tickets	zendesk_tickets	Upsert by primary key, incremental on updated-at
users	zendesk_users	Upsert by primary key, incremental on updated-at
organizations	zendesk_organizations	Upsert by primary key, incremental on updated-at
macros	zendesk_macros	Upsert by primary key, incremental on updated-at
satisfaction ratings	zendesk_satisfaction_ratings	Upsert by primary key, incremental on updated-at

Zendesk 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 Support API v2
Authentication	OAuth 2.0, API key, HTTP Basic — Zendesk supports Basic auth with an API token or agent password, and OAuth 2.0 via either the authorization-code flow (per-user, scoped) or the client-credentials flow for server-to-server pipelines; OAuth is now the recommended method and existing API-token integrations are being pushed to migrate.
Pagination	cursor — Cursor pagination is requested with `page[size]` (most endpoints cap it at 100) and returns `meta.has_more`/`meta.after_cursor`; omitting `page[size]` falls back to offset pagination, which Zendesk documents as unreliable past large offsets.
Rate limit	200-2,500 requests/minute to the Support/Help Center API depending on plan (Team 200, Professional 400, Enterprise 700, High Volume add-on 2,500 per minute).
Incremental cursor	cursor (or start_time on the time-based endpoint) — The recommended cursor-based incremental export, GET /api/v2/incremental/tickets/cursor.json, takes `start_time` only on the first call and an opaque `cursor` from every response after that; the older GET /api/v2/incremental/tickets.json?start_time=... endpoint still works but is superseded for tickets, users, and custom object records.
Webhooks	Yes — Webhooks (event subscriptions, or triggers/automations connected to a webhook target)
Bulk export	Yes — Incremental Ticket/User/Organization Export API
Deletes detectable	Yes — Deleted tickets remain in the incremental export response (status marked deleted) unless `exclude_deleted=true` is passed; fields are replaced with scrubbed placeholders 30 days after deletion and the record drops out of exports after 90 days.

Official API reference

What bites when replicating Zendesk

The cursor-based incremental export endpoint (`/api/v2/incremental/tickets/cursor.json`) never returns data for the most recent 60 seconds, so polling more often than once a minute just returns an empty `after_cursor` page.
Incremental export endpoints return up to 1,000 records per page, but that cap can be exceeded when multiple records share the same timestamp, so a naive `per_page` assumption will under-count.
The incremental export family is separately rate-limited to 10 requests/minute (30/minute with the High Volume add-on), independent of the general 200-2,500 requests/minute Support API limit.
Regular list endpoints only get cursor pagination when you pass `page[size]`; omitting it silently falls back to offset pagination, which Zendesk's own docs say degrades past roughly 10,000 records.

Compare this against every other documented API

Popular destinations for Zendesk

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 connector FAQ

What Zendesk data does the connector extract?: 5 objects: tickets, users, organizations, macros and satisfaction ratings. Each lands in its own table with types preserved; history-style objects (0) load as append-only streams.
Is the Zendesk 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 data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Zendesk → destination pair has its own page with the object-to-table mapping.

Related sources

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

Early access

Launch your Zendesk pipeline with guided onboarding

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