Integrations
What connects today, what is a directory listing, and what a connection actually is.
Integrations in the main sidebar (/integrations) is a directory of other
products, and it is honest about a distinction most app stores blur: a handful
of entries connect today, and the rest are listings you can ask us to build.
The header says so in numbers, and the numbers are computed from the catalogue rather than written down: on the shipped catalogue of 707 entries, ten connect today and the other 697 are directory listings.
That ratio is the point. Auralis' position is to integrate rather than compete — the AI agents are unbundled from the helpdesk on purpose so they can drive somebody else's — and a catalogue that implied 707 working connectors would make that claim dishonest.
The ones that connect
They fall into three groups, which work in different directions.
Three helpdesks you connect to. Zendesk, Freshdesk and Intercom. You give Auralis a credential for your account there, and Auralis reads from it. See Connecting Zendesk, Freshdesk and Intercom.
Three assistants that connect to you. Claude, ChatGPT and Gemini. These are the MCP entries, and there is no credential to paste because the direction is reversed: the assistant is the client and your helpdesk is the server. Opening one shows your workspace's own MCP connection URL, a copy button, and the setup steps for that client.
If MCP is off for your deployment
The card says so in words — MCP is not switched on for this helpdesk — and prints no URL. If we cannot determine whether MCP is served at all, it says that too, rather than guessing a URL you could not use.
Four guided setups. Slack, Microsoft Teams, Zapier and e-automate reach
their own screens rather than a credential form on this page. Slack and Teams in
particular are channels: /integrations/slack and /integrations/teams both
redirect to /channels/slack and /channels/teams, because they were briefly
split across two pages and clicking Manage landed you on settings that told
you to go somewhere else to switch the thing on.
The directory
Everything else is a catalogue of products we have not built a connector for. It is there so you can tell us what you need rather than guessing whether we support it.
Opening a listing gives you a description and a Request activation form with one optional field — Anything we should know? (optional) — up to 2,000 characters. Filing one records the request against your workspace and emails whoever handles them.
Two things worth knowing:
- Requesting twice is harmless. A second request for the same product is recognised as the same request. No duplicate row, no second email.
- The card remembers. Reload the page and an entry you have already asked for reads Requested, with the date.
You cannot request something that already connects: asking is refused with a note to connect it instead.
Use the Availability filter in the left-hand rail to collapse the directory to Available now, which is usually what you want after the first browse. The filters live in the page address, so a filtered catalogue is a link.
What a connection actually does — and does not
This is where expectations most often run ahead of the product, so it is worth stating flatly.
A connection is a stored, verified credential. That is all it is. Connecting Zendesk does not start a sync, does not mirror tickets, does not post notifications anywhere, and does not poll on a schedule. There is no job enqueued and no scheduler involved.
What a connection is for, today, is migration. The Migrate surface at
/settings/migrate reads these connections to scan and import your existing
tickets and articles, and that only happens when somebody runs it. There is no
field mapping and no "sync now" on the Integrations page, because there is
nothing continuous behind it.
If what you are looking for is your AI agent's own connection, that is elsewhere: it is configured under Aura AI, not here.
Who can do what
| Action | Floor |
|---|---|
| Browse the catalogue, the directory and filed requests | Viewer |
| File an activation request | Editor |
| Connect, test, disconnect | Admin |
Below the floor the buttons are absent rather than greyed out, with a line saying which role the action needs, and the page tells you it is read-only for you. A row menu with nothing in it is not rendered at all. That is deliberate: the interface shows the same answer the runtime would give, rather than offering an action that would come back refused.
The connected list
Connections you already have are listed above the store, with the product's name, the account the credential belongs to, and its state. That list renders even if the catalogue itself fails to load, because it is the part you need in a bad moment.
| State | What it means |
|---|---|
| Connected | The credential was verified and is working. |
| Pending | Credentials are stored but were never checked. This only happens for connectors that are not finished. |
| Action needed | Anything else, including an error. |
An unrecognised state deliberately reads as Action needed, never as Connected. A false green is worse than an unexplained amber. When a row says Action needed, the last error from the other product is shown beside it, in that product's own words.
Next
- Connecting Zendesk, Freshdesk and Intercom
- MCP — driving the helpdesk from Claude, ChatGPT or Gemini.
- Channels — Slack and Microsoft Teams live here.
Approvals
The queue where a person decides what an AI agent may do: where requests come from, who can decide, what approving actually does, and expiry.
Connecting Zendesk, Freshdesk and Intercom
The three credential connections: what each needs, how the test-before-store rule works, and testing and disconnecting.