Integrations

Integrations is the one place an app is connected to your workspace. You connect it once here, and the places that use it (today, your agents' custom tools) pick it from a list instead of each asking for a key.

Open it from Manage → Integrations in the console.

What you can connect #

Booking calendars still connect from their own card on each calendar under Calendar → Booking rules.

Who can connect #

Owners and admins connect, reconnect, rename and disconnect apps. Members can see what is connected and what uses it, but not change it.

Connecting is for the whole workspace, not just you. You can connect more than one account of the same app.

Connect an app #

1. Open Integrations and choose the app under Add an app.
2. For Google or Microsoft, select Continue and sign in on the app's own page. Amomic-AI never sees your password. You come straight back to Integrations, and the connection appears under Connected.
3. For a named app such as HubSpot or Notion, select Add key, paste the key (the sheet links to where the app makes one) and select Check & save. We try the key with the app first: if the app refuses it, nothing is saved and you're told why. If the app can't be reached just then, the key is saved and checked again later. If your app only accepts calls from approved IP addresses (Brevo can turn this on by itself), turn that off: Amomic-AI's servers don't have a fixed address, and the sheet tells you when this is the problem.
4. For any other app with an API key, give the connection a name your team will recognise, paste the key, and say where the app expects it (an Authorization: Bearer header, or a header with a name you type).
5. For a mailbox, enter the email address and password. We fill in the mail server from the address; change it if your provider says otherwise. Many providers need an app password made in their security settings, not your normal one.

Only the admin who started a connection, signed in to this workspace, can complete it. A connect link sent to someone else never adds their account to your workspace.

Use the search box or the category filters to find an app. If yours isn't listed but has an API, Any app with an API key works with it.

Where a named app's key can go #

A key you add for a named app is only ever sent to that app's own API: a HubSpot key to api.hubapi.com, api.hubspot.com or api-eu1.hubapi.com, a Notion key to api.notion.com, and so on. In a tool's Sign in with list, a named key whose app doesn't match the tool's URL is shown but can't be picked. A key added under Any app with an API key goes wherever you point it.

If your organisation needs an IT admin #

Some Microsoft 365 organisations only let an IT admin approve new apps. When that happens, Integrations shows Ask your IT admin with a link to send them. Once they approve Amomic-AI, connect again.

Use a saved key in a tool #

When you add or edit an API or MCP source on a knowledge base, the Sign in with list offers your saved API keys. Pick one and the tool signs its requests with it; the header fields hide, and anything you had typed there is kept as a fallback. Admins can also add a key right from the form: when the tool's URL is a named app's API (say https://api.hubapi.com/...), the list offers + Add a HubSpot key…; otherwise + Add an API key….

Keeping the key in Integrations means it is stored encrypted in one place and your team picks it from a list, instead of pasting it into each tool.

When something stops working #

Every connection is checked daily: Google, Microsoft, mailboxes and named-app keys are tried against the app itself, and every API key is also checked each time a tool uses it. Select Check now in a connection's ⋯ menu to check it straight away (a key under Any app with an API key has no check of its own; it's judged by use). When an app stops letting Amomic-AI in (a password change, a key that was reset, access removed in the app), three things happen:

• the connection moves to the top of Connected with Reconnect needed and a plain explanation;
• the knowledge base whose tools use it shows a banner with a way to fix it;
• owners and admins get one email with a Reconnect button. It's sent once per break, not on every failed call.

Until it's reconnected, agents say they can't look that up rather than guess.

To fix a Google or Microsoft connection, select Reconnect and sign in again as the same account. For an API key, add the new key, pick it under Sign in with on each tool that used the old one, then disconnect the old one. The banner and the email both take you to adding the new key.

Disconnect #

Open the ⋯ menu on a connection and choose Disconnect. Amomic-AI stops using it and deletes the saved sign-in; nothing in the app itself is changed.

If a tool still uses the connection, Integrations lists those tools first. Remove the connection from them for a clean disconnect, or choose Disconnect anyway: those tools fall back to headers typed on the tool itself, if any, and otherwise send no sign-in.

Each connection keeps a record of who connected, reconnected, renamed or disconnected it, and when it broke or recovered.

Plan limits #

The header of Integrations shows how many you've used. Reconnecting an existing connection never counts as a new one.

What we store #

Tokens, keys and passwords are kept in encrypted secret storage and are never shown again, in the console or anywhere else. The console only ever sees a connection's name, status and what uses it. When a workspace is deleted, its connections and their saved sign-ins are deleted with it.