- Mirror organizations and end-users with Zendesk incremental exports, paced for the 10 requests/minute export limit
- Apply changes on linked Zendesk records to Iris companies and contacts on a schedule
- Push Iris edits back via bulk jobs (create_many / update_many) in batches of up to 100
- Name or e-mail collisions are flagged for manual matching — never auto-merged, and nothing is ever deleted
- 1,208 catalogued routes (609 read-only) can be tried by an admin from the Iris integrations hub
- Field mapping scoped per tenant; sync runs under the API user's own Zendesk permissions
Zendesk API Connector
Keep Zendesk organizations and end users in step with Apivom Iris: incremental exports mirror them into your tenant, changes on linked records flow back through Zendesk bulk jobs, conflicts are surfaced instead of merged — connected with your subdomain, an admin e-mail and an API token.
What you can do
Use cases
- Support sees the same company as sales — Organizations in Zendesk stay matched to Iris companies, so agents and account managers share tax ids, segments and owners without re-typing them.
- Clean end-user records from the CRM — Contact changes made in Iris — new e-mail, new role, new company — reach the linked Zendesk end-user in the next scheduled push.
- Onboard a large Zendesk instance safely — Incremental exports bring tens of thousands of organizations and users in without tripping rate limits, and every ambiguous match waits for a human decision.
Zendesk's Support API covers tickets, users, organizations, groups, custom fields, triggers, incremental exports and much more under each customer's own subdomain. Apivom Iris uses it to keep the people and companies you support aligned with the ones you sell to. The connection takes your subdomain, an admin's e-mail and an API token; the API token runs with that user's permissions, which is why incremental exports — the mechanism the mirror relies on — require an administrator (an agent token falls back to Zendesk's search export, which cannot see deleted records). On a schedule, Iris pulls organizations and end-users through Zendesk's incremental export endpoints, paced to respect the ten-requests-per-minute limit, and applies changes on records already linked to Iris companies and contacts. In the other direction, edits made in Iris on linked records are pushed back with Zendesk's bulk create_many and update_many jobs in batches of up to 100. The sync is deliberately conservative: a name or e-mail collision is surfaced for a person to resolve rather than merged, and the connector never deletes on either side. Tickets themselves are not synchronised.
Zendesk subdomain + API user e-mail + API token (Basic auth, token mode). Requests run with that user's Zendesk permissions — incremental exports need an admin. The token is kept encrypted in your Iris tenant; Apivom Atlas only forwards the request to your subdomain and logs it.
Frequently asked questions
What exactly is synchronised, and what is not?
Organizations and end-users, in both directions, for records linked between Zendesk and Iris. Tickets, groups, triggers and other objects are catalogued and can be called from the hub, but they are not part of the scheduled sync. Nothing is deleted on either side.
How does the connector avoid Zendesk rate limits?
The mirror uses Zendesk's incremental export endpoints and is paced for their 10 requests/minute limit; outbound changes are grouped into bulk jobs of up to 100 records, so a large push costs a handful of calls instead of thousands.
What happens when two records look like the same company or person?
The connector does not guess. Name or e-mail collisions are listed as conflicts for an administrator to match or dismiss; until that decision the record is left untouched on both sides.
Does Apivom charge per API call for this connector?
No. Connectors are part of your Apivom tenant and are not metered in the Atlas portal. The vendor's own pricing, quotas and rate limits still apply to the account you connect — Apivom paces its calls to stay inside them and shows every call in your tenant's integration log.
Where are my credentials stored and who can see the traffic?
Apivom Atlas is a stateless gateway: it never stores vendor credentials or tokens. The Apivom product that connects keeps the credential encrypted in your tenant database, and every request and response is logged in your tenant only — your data is never shared across tenants.
More Atlas integrations
AI integration guide (llms.txt)
Machine-readable markdown — feed it to your AI assistant as integration instructions.