Support & Ticketing · Integration
Dixa
Add Dixa to your product for your customers, and give your AI agents governed access to it.
Dixa's API is served from dev.dixa.io rather than a dixa.com subdomain, and takes a bearer token minted per integration in the Dixa admin area. Conversations are the central object, identified by a numeric csid, and carry channel (email, chat, voice, messenger), state, assigned agent and custom attributes; messages hang off /v1/conversations/{csid}/messages. Tagging is not a field update: you add and remove a tag by PUT and DELETE against /v1/conversations/{csid}/tags/{tagId}, using the tag's UUID rather than its label, so any integration needs to resolve tag names first. End users are separate records under /v1/endusers with their own identifiers, and merging or anonymising them has dedicated endpoints because Dixa treats GDPR erasure as a first-class operation. Bulk historical extraction is not done through the same API; Dixa exposes a separate exports surface for that, and hammering the conversation endpoints instead will hit per-endpoint rate limits. fastn holds each customer's Dixa token, refreshes it, and keeps every conversation read and write attributed to the right tenant.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Dixa workspace so your product can read their conversations and post replies without a shared token
Sync end user records and their conversation history into your own customer timeline view
Apply tags to conversations automatically based on classification your product runs, resolving tag UUIDs first
Surface open conversation counts per agent and channel in an operations dashboard
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent draft a reply on a conversation and leave it for human approval, with each draft audited per tenant against that tenant's own Dixa token
Have an agent read the last inbound message on a conversation and tag it by topic
Allow an agent to look up an end user's prior conversations before answering a repeat contact
Example prompt
How many Dixa conversations are still unassigned on the email channel, and what are they about?
Set up Dixa in 4 steps
- 01Enable the Dixa connector from your fastn dashboard.
- 02Have each customer authorise their own Dixa 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 Dixa integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Dixa integration without building it. Your customers connect their own Dixa 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 Dixa update is not your on-call problem.
- One integration serves your product and your agents. The same governed Dixa 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
Zendesk
Intercom
FrontOften used alongside
Tools the same teams tend to run next to Dixa, across other categories.
Salesforce
HubSpot
Slack
NetSuiteDixa integration FAQ
How do I add a Dixa integration to my product?
Enable the Dixa connector in your fastn dashboard, then let each customer authenticate their own Dixa account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Dixa client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Dixa account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Dixa 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 Dixa integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Let an agent draft a reply on a conversation and leave it for human approval, with each draft audited per tenant against that tenant's own Dixa token
Who maintains the Dixa integration?
fastn does. When Dixa 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 Dixa 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 Dixa?
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 Dixa integration?
A common starting point: let a customer connect their own Dixa workspace so your product can read their conversations and post replies without a shared token. 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 Dixa integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Dixa does not change your per-connector cost. You can start free with 3 connected accounts.
Add Dixa to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.