Support & Ticketing · Integration
Aidbase
Add Aidbase to your product for your customers, and give your AI agents governed access to it.
The Aidbase API is served from https://api.aidbase.ai/v1 with a bearer token, and an unauthenticated call comes back as a JSON body with success false and a message saying the API key is missing rather than an empty 401. Keys are created with an explicit permission selection, so a key that works for reading knowledge items can legitimately fail on chatbot writes and the failure looks like a scope problem rather than a bad key. The surface is split into four groups that map to how support actually arrives: knowledge for documents and articles, chatbot for the bots and the knowledge attached to them, ticket form for form submitted tickets, and email inbox for the mail channel. Every list endpoint is paginated with a default page size of 25 and a limit parameter, so any sync that assumes a full result set will silently truncate. fastn holds each customer's key with its permission scope and keeps the connection maintained as keys change.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Aidbase workspace so tickets and knowledge stay in their account
Push your product documentation into a customer's knowledge base so their chatbot answers from current content
Read tickets from the ticket form and email inbox channels into your own queue view
Attach or detach knowledge items from a specific chatbot when a customer changes what it should cover
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent search a tenant's knowledge items and draft a reply grounded in what is actually published
Have an agent create a knowledge item from a resolved ticket so the same question is answered next time
Audit per tenant which tickets and knowledge items an agent read or wrote, given keys carry explicit permission scopes
Example prompt
What are the most common unanswered questions coming into our support inbox this week?
Set up Aidbase in 4 steps
- 01Enable the Aidbase connector from your fastn dashboard.
- 02Have each customer authorise their own Aidbase 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 Aidbase integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an Aidbase integration without building it. Your customers connect their own Aidbase 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 an Aidbase update is not your on-call problem.
- One integration serves your product and your agents. The same governed Aidbase 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 Aidbase, across other categories.
Salesforce
HubSpot
Slack
NetSuiteAidbase integration FAQ
How do I add an Aidbase integration to my product?
Enable the Aidbase connector in your fastn dashboard, then let each customer authenticate their own Aidbase account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Aidbase client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Aidbase account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Aidbase 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 Aidbase 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 search a tenant's knowledge items and draft a reply grounded in what is actually published
Who maintains the Aidbase integration?
fastn does. When Aidbase 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 an Aidbase 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 Aidbase?
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 Aidbase integration?
A common starting point: let a customer connect their own Aidbase workspace so tickets and knowledge stay in their account. 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 Aidbase integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Aidbase does not change your per-connector cost. You can start free with 3 connected accounts.
Add Aidbase to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.