Support & Ticketing · Integration
Zendesk
Add Zendesk to your product for your customers, and give your AI agents governed access to it.
Zendesk is built around the ticket and the comments on it, so a Zendesk integration reads and writes tickets, public replies and internal notes, users and organizations, applies the macros agents already rely on, and reads the views they work from. Side conversations hang off a ticket for the vendor or colleague loop. Two details bite. Every account lives at its own subdomain, and that subdomain is part of the address of every request, so the tenant is in the URL rather than in a parameter. And custom fields are numeric ids issued per account, with ticket fields and user fields numbered separately, so an id meaning priority in one account means nothing in the next. fastn keeps each subdomain's credentials per tenant and tracks the API as it changes.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Have each customer connect their own Zendesk subdomain so your product opens tickets in the account their agents are actually staffing.
Write a public reply, or an internal note nobody outside the team sees, so the audit trail lives on the ticket rather than in your own logs.
Resolve the numeric ticket field and user field ids per account at setup, so a customer's own priority or product field gets filled correctly.
React when a ticket is created, escalated or solved, and open a side conversation when a third party has to be pulled in.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads a ticket's whole comment thread and the organization behind the requester before drafting anything.
An agent applies an approved macro and the fields it sets, with the macro it chose recorded on the call.
An agent reports what is sitting in a given view right now, for one account only.
Example prompt
Summarise the comments on this ticket and tell me which macro the team usually applies to it.
Set up Zendesk in 4 steps
- 01Enable the Zendesk connector from your fastn dashboard.
- 02Have each customer authorise their own Zendesk account, so calls run under their credentials rather than a shared key.
- 03Decide which conversations, customers and tags your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Zendesk integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Zendesk integration without building it. Your customers connect their own Zendesk account inside your product and work their conversations, customers and tags there, with no per-customer code on your side.
- Handle the part that actually costs time: support volume is spiky, and support teams notice latency immediately. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Zendesk update is not your on-call problem.
- One integration serves your product and your agents. The same governed Zendesk connection powers in-product features and gives AI agents scoped, audited access, so you let support work your customers' queues without leaving your product without wiring it twice.
Used by these teams
Compare with
Freshdesk
Intercom
Zoho DeskOften used alongside
Tools the same teams tend to run next to Zendesk, across other categories.
Salesforce
HubSpot
Slack
NetSuiteZendesk integration FAQ
How do I add a Zendesk integration to my product?
Enable the Zendesk connector in your fastn dashboard, then let each customer authenticate their own Zendesk account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Zendesk client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Zendesk account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Zendesk account and only ever sees their own conversations, customers and tags. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Zendesk integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reads a ticket's whole comment thread and the organization behind the requester before drafting anything.
Who maintains the Zendesk integration?
fastn does. When Zendesk changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can an agent resolve a Zendesk conversation end to end?
An agent can read the full history, post replies, change status and route within the permissions you grant it. Every action is attributed and audited, so you can show exactly what the agent did rather than inferring it.
Do I get notified the moment something changes in Zendesk?
Yes, through event triggers rather than polling, so your product reacts to a new or escalated conversation in near real time.
What can I build with the Zendesk integration?
A common starting point: have each customer connect their own Zendesk subdomain so your product opens tickets in the account their agents are actually staffing. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Zendesk integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Zendesk does not change your per-connector cost. You can start free with 3 connected accounts.
Add Zendesk to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.