Customer Support

Zendesk Support Data Extractor

Vern's Zendesk Support extractor imports a new user's customer support data — tickets, users, account attributes, and article attachments — into your product through a single managed migration, handling Zendesk Support's auth, pagination, and rate limits for you. It's built for teams onboarding customers off Zendesk Support who want their data in your app from day one.

Start migration

Browse all extractors

Zendesk Support

SaaS API (REST)

Managed auth, retries, and throttling

Normalized JSON, CSV, and DB-ready output

Cleaned JSON, CSV, and DB-ready output

Export coverage

Know exactly what Vern pulls before you migrate.

Objects Vern extracts

Vern extracts the full set of queryable Zendesk Support objects (42 total), including: Account Attributes, Article Attachments, Article Comment Votes, Article Comments, Article Votes, Articles, Attribute Definitions, Audit Logs, Automations, Brands, Categories, Custom Roles, Deleted Tickets, Group Memberships, Groups, Macros, Organization Fields, Organization Memberships, Organizations, Post Comment Votes, Post Comments, Post Votes, Posts, Satisfaction Ratings, Schedules, Sections, Sla Policies, Tags, Ticket Activities, Ticket Audits, Ticket Comments, Ticket Fields, Ticket Forms, Ticket Metric Events, Ticket Metrics, Ticket Skips, Tickets, Topics, Triggers, User Fields, Users, and Users Identities. 12 of these support incremental change tracking, so syncs pull only what changed.

Output schema

Normalized JSON per object with referential keys preserved, so the relationships between your user's records survive the import. Timestamps are returned in ISO 8601. Delivered as JSON or CSV, or loaded straight into your own application database or pushed to your API — whatever your product expects.

Where it can land

Your own application database (Postgres, MySQL), a direct push to your API or webhook, or JSON/CSV files, plus another customer support system (Canny, Customerly, Dixa) when a user is switching tools.

Source details

Built for the source type shown above, with extractor content refreshed from the collection record.

Managed by Vern

The details you normally have to build yourself.

Authentication

OAuth 2.0 (Authorization Code flow). Your new user authorizes Zendesk Support once during onboarding — their credentials never touch your code. Zendesk Support access tokens are short-lived and refresh tokens roll on the provider's own schedule, so Vern manages the full token lifecycle and refresh and the import never drops midway. See Zendesk Support's authentication guide.

Pagination

Vern detects and handles Zendesk Support's paging model (cursor, page-number, or offset) internally and returns one consistent, de-duplicated result set — so you import a user's complete data without ever managing page tokens.

Rate limits and gotchas

Zendesk Support enforces its own API rate limits (see Zendesk Support's rate-limit docs). Vern queues and throttles requests internally so importing a new user's data never trips a 429 — even on a large account.

OAuth-based sources expire access tokens frequently and require a working refresh flow — a dropped refresh is the most common cause of a half-finished import. Vern owns the refresh loop so a new user's onboarding completes even on a long extraction.

API quickstart

1. Create a migration for Zendesk Support
curl -X POST https://app.vern.so/api/v1/migrations \
  -H "x-api-key: $VERN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "name": "Zendesk Support → Postgres", "source": "Zendesk Support" }'
→ { "migration_id": "mig_..." }
2. Generate the extraction recipe (pulls live via the Zendesk Support API)
curl -X POST https://app.vern.so/api/v1/migrations/$MIGRATION_ID/runs \
  -H "x-api-key: $VERN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "kind": "generate", "extract_via_api": true }'
3. Run the approved extraction
curl -X POST https://app.vern.so/api/v1/migrations/$MIGRATION_ID/runs \
  -H "x-api-key: $VERN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "kind": "execute" }'
4. Download the normalized CSV export
curl https://app.vern.so/api/v1/migrations/$MIGRATION_ID/exports/{template} \
  -H "x-api-key: $VERN_API_KEY" -o zendesk-support_export.csv

A cleaner way to extract without rebuilding source-specific plumbing.

View docs

Common questions

Can I keep a user's Zendesk Support data in sync after the first import? Yes — 12 Zendesk Support objects support incremental change tracking, so after the first full import Vern pulls only what changed on re-run.

Can I move a user from Zendesk Support to Canny? Yes — Vern normalizes the Zendesk Support data model into typed tables that map cleanly onto Canny and into your own product.

What does it cost to read the Zendesk Support API? Zendesk Support's own API access follows Zendesk Support's pricing/plan; Vern is billed separately per import. Check Zendesk Support's developer docs for their current limits.