Skip to content
DataSquaresDocs
datasquares.aiSign inStart free

Connect DataBusiness Apps

Zendesk

Zendesk is in Preview in the connection wizard: it is built on Zendesk’s documented API and has not yet been proven against a live account, so check the imported tables before relying on them. Sign in with your own Zendesk OAuth client, or use an API token until Zendesk retires them on 30 April 2027.

  1. In DataSquares, open Data Sources and choose Connect Source. The Connect a data source page opens.

  2. Pick Zendesk on that page (search or browse by category).

  3. Fill in the connection details below, then test the connection and save.

Connection details

Section titled “Connection details”
Field What to enter
Subdomain The part before .zendesk.com. e.g. yourcompany
Agent email e.g. you@company.com Only with an API token.
API token Admin Center → Apps and integrations → APIs → API tokens. Stored encrypted and never shown again. Only with an API token.
OAuth client identifier Admin Center → Apps and integrations → Zendesk API → OAuth Clients: a Confidential client, its unique identifier. Only when you sign in with Zendesk.
OAuth client secret Stored encrypted and never shown again. Only when you sign in with Zendesk.

Test Connection reads one page of records with these values; nothing is saved until you import.

Signing in

Section titled “Signing in”

Instead of pasting a key, choose Sign in with Zendesk in the form: you approve access on Zendesk’s own page and come back to the wizard signed in, then pick the tables. DataSquares keeps the sign-in encrypted and renews it before every refresh; if Zendesk stops accepting it, the refresh says so — sign in again.

The sign-in uses an OAuth client you create in Zendesk (a confidential one). Enter its identifier and secret in the form, and allow the redirect URL the form shows — on DataSquares Cloud that is https://api.datasquares.ai/api/oauth/callback.

Tables

Section titled “Tables”

Pick the tables to import — each one becomes a table in the source:

Table What it holds
tickets Tickets
users Users
organizations Organizations
groups Groups
ticket_fields Ticket fields — Names for the custom-field ids on tickets.

Every table is read through all of its pages, nested fields become parent.child columns, and the whole set is imported at once: the import’s row and size limits count the picked tables together, and if they pass one, nothing is imported and the message says which table and which limit. Refresh the source on a schedule, or by hand, to re-read every table; a table that comes back empty is refused rather than emptied unless you allow it. Nothing is ever written to Zendesk.

The requests follow Zendesk’s API reference.

Section titled “Related”