Zendesk

A read-only OAuth integration that syncs Zendesk tickets into Rippit on a schedule. For what applies to every integration, see how data integrations work. For the security model, see Data integration security.

​

Connection summary

​

Before you connect

Rippit can read only what the authorizing account can read. Use a dedicated Zendesk service account so you control what it can see, the audit trail is unambiguous, and the connection does not break when someone leaves. You will need that account’s Zendesk subdomain and admin credentials. You authenticate against Zendesk, never against Rippit, and Rippit never receives the password.

​

Data handling

​

API endpoints

The show_many.json?ids= endpoints are batch lookups of specific records, not list sweeps. Rippit requests only the tickets, users, and organizations already referenced by data it has synced. Agents and admins are the exception: that roster is swept in full, via /users.json.

​

Sync behavior

Sync runs on a schedule rather than on ticket events, which is why data is hours behind rather than immediate.

​

Rate limiting

• Requests are batched and cursor paginated to minimize call volume
• 429 responses trigger backoff and retry rather than immediate repeat
• Workers pace against remaining rate limit rather than competing with each other
• Other integrations sharing your Zendesk instance are not starved

​

Limiting ingestion scope

Set at connection time: