Ship deep Zendesk integrations in days

Zendesk Support spreads tickets, users, and organizations across dozens of APIs, and every account adds its own ticket fields, forms, and triggers. With Ampersand, you can get this integration live for your customers in days.

Schedule a demo See Zendesk guide

Build a custom data model to handle complex configurations

No two Zendesk accounts are the same. Every customer has custom ticket fields, forms, and statuses, and their own triggers and views. AI agents need infrastructure that understands Zendesk at the per-tenant level.

3 / 4 customers

3 / 8 customers
  • Customer A: Ticket (standard), User (standard), Organization (standard)
  • Customer B: Ticket (standard), Group (standard), Macro (standard)
  • Customer C: Ticket (standard), Ticket Form (standard), Custom Status (standard)

Enable software and agents to take bi-directional action

With Ampersand, your engineers don’t need to learn Zendesk’s ticketing, incremental export, and admin APIs. Simply declare the actions you want your agents to take: read, write, proxy.

Example. Write: “Open a ticket when my agent flags a refund request.”

  1. Ampersand uses this customer’s Zendesk OAuth token.
  2. Ampersand writes to the ticket fields this customer mapped, custom fields included.
  3. Ampersand creates the ticket through the Tickets API.
  4. Ampersand returns the new ticket’s ID to your product.

Ensure your Zendesk integration is always available

  • Managed auth

    Fully offload Zendesk OAuth. Ampersand stores and refreshes tokens for every customer’s Zendesk account.

  • Custom ticket fields

    Read and write the custom fields each customer adds to tickets and requests, mapped to your product’s own fields.

  • Schema drift detection

    Get notified when fields are created, deleted, or changed in any customer’s Zendesk, before the change breaks your integration.

Not all Zendesk integrations are created equal

Zendesk Support is where many support teams keep every customer conversation. With Ampersand, your developers can create a best-in-class Zendesk integration.

In-House DIY Build Unified APIs Embedded iPaaS Ampersand
Data schema that works for all customers Lots of switch statements and special casesOnly access standard objects and fieldsBuild customer-specific workflows Flexible model with mappings
Object coverage Write and maintain clients for tickets, users, and every admin APIOnly common models and their standard fieldsLimited to the objects its prebuilt actions cover Tickets, users, organizations, and account configuration
Schema drift protection Manual incident debuggingNot supportedNot supported Get notified about schema changes
OAuth token custody You own the tokens, but you also have to manage refreshesVendor lock-inVendor lock-in Export at any time via API
Integration workflow Imperative custom codeSingle API clientDrag-and-drop, not integrated with Git Declarative manifest you can version control
Build vs. Buy Unified API vs. Ampersand

The Zendesk objects your agents can read and write

Ampersand reads and writes Zendesk Support tickets, users, organizations, and account configuration, with custom fields on tickets and requests.

Objects What’s included Read Write
Tickets and people
  • Tickets
  • Requests
  • Suspended tickets
  • Users
  • Organizations
  • Groups
  • Organization memberships
  • Group memberships
Supported Supported
Fields and forms
  • Ticket fields
  • Ticket forms
  • User fields
  • Organization fields
  • Custom statuses
Supported Supported
Workflow and configuration
  • Triggers
  • Trigger categories
  • Automations
  • Macros
  • Views
  • Tags
  • Brands
  • Targets
Supported Supported
Events and metrics
  • Ticket events
  • Ticket metric events
  • Instance values
  • Attribute values
Supported Not supported

Incremental reads cover tickets, users, organizations, ticket events, ticket metrics, attributes, and instance values.

See every object in the docs

Questions people ask before they book a demo

  • Which Zendesk objects can I read and write?

    You can read and write tickets, requests, users, organizations, groups, ticket fields and forms, triggers, macros, views, and more. Ticket events, ticket metric events, and instance values are read-only.

  • Can my integration connect to any customer’s Zendesk?

    Yes, once Zendesk approves a global OAuth client for your app. Start in a Zendesk account whose subdomain begins with d3v- and give your OAuth client an identifier that begins with zdg-, so you can request one later.

  • Who on the customer side needs to connect Zendesk?

    A Zendesk admin. Zendesk’s API permissions require admin credentials for this integration.

  • Does Ampersand offer a unified API?

    Ampersand doesn’t offer a unified API. It works with Zendesk’s own objects and fields as each customer sets them up, which differs from how a unified API works. We also give you the primitives to build your own unified data model.