Integrations in a Conversation

An Integration is a tool of your company that the agent can work with, such as a BI tool. Admins register it for the Tenant (Manage Integrations), and the agent then calls its tools in your Conversations, as you.

Which Integrations a Conversation has

On Start, where you write the first message of a new Conversation, select Integrations below the message field. It lists every Integration you can use, each with a tick: all are selected. Select one to untick it, and the agent won’t use it in this Conversation. An Integration you aren’t connected to yet has a small dot, named Not connected or Needs reconnecting for screen readers; it stays selectable, and the agent asks you to connect it when it needs it.

When you send the first message, the selection becomes fixed for the rest of the Conversation. In the Conversation, Integrations below the message field lists it without letting you change it, with “Unavailable” for one you can no longer use. Without a choice, the Conversation gets every Integration you can use. An Integration an admin registers later is available from your next Conversation on. One that is deactivated or taken from you stops working from the next Turn on, and the agent tells you if your request needs it.

Connect an Integration

Some Integrations ask you to sign in first, so the agent acts as you there, with your own access. Open your account menu and select Integrations. Each Integration shows whether you are connected, not connected, need to reconnect, or need no sign-in. Select Connect: you go to the server’s own sign-in and come back to the page, with the Integration connected. Select Disconnect to withdraw it: your tokens are deleted, and revoked at the server where it supports that.

The agent has the tools of an Integration with a sign-in only once you are connected. If you cancel at the server, or the sign-in takes more than ten minutes, the page says so and nothing is connected; start again from the Integrations page. Only you can finish a sign-in you started, and only once.

You sign in once, not every hour: the agent renews your sign-in on its own, also when you work in several Conversations at once. If the server refuses to renew it, because the sign-in ended or you withdrew it there, the Integration shows Needs reconnecting on your Integrations page and the agent has none of its tools until you select Reconnect and sign in again. The agent tells you in a Conversation when your request needs such an Integration.

Enter your own API key

Some Integrations don’t sign you in at a server; they take a personal API key instead. On the Integrations page such an Integration shows Enter API key. Select it, paste the key you got from that system and select Save key. The agent sends your key, and nobody else’s, whenever it works with the Integration for you.

If the agent needs an Integration that takes a key and you haven’t saved one, its card in the Conversation says so. Select Enter API key: the Integrations page opens with the key dialog, and after you save the key you return to the Conversation, where you select Continue.

Your key is stored encrypted and never shown again, not even to you. To rotate it, select Replace API key and enter the new one; Disconnect deletes it. A key must be one line of at most 2,048 characters. If you paste a key into a message, it is masked in the record of the Turn that anyone else may read when you rate it.

Register your own Integration

With the Right Register Personal Integrations, which the Role Member holds by default, you can register any remote MCP server for yourself, even one nobody in your Tenant has vetted. On the Integrations page select Register a Personal Integration, enter the server’s address and select Check address: we ask the server whether it answers as an MCP server and suggest how it signs you in. If the server wants a personal API key, it refuses the check without one: select This server takes my own API key and name the header it is sent in (Authorization sends the key as a Bearer token). Then give it a name and confirm the warning.

The warning matters: whatever the agent sends to a Personal Integration leaves the platform, and neither we nor your admins have checked the server. Register only servers you trust. You can’t save the Integration before you confirm.

A Personal Integration is yours alone. Nobody else in your Tenant can see or use it, admins included. You connect it and use it in a Conversation like any other Integration, and it appears among the Integrations of a new Conversation. You can have 20; the page shows how many you have before you reach the limit. Select Rename to change its name, or Delete to remove it together with your connection to it. Your admins’ Audit Log records that you registered, renamed or deleted one, with the server’s host, never what was sent to it.

If you lose the Right, your Personal Integrations stay on the page as unavailable, with a note. The agent doesn’t use them, and a new Conversation doesn’t offer them, but you can still rename and delete them. They work again when you get the Right back.

The connect card

When your request needs an Integration you haven’t connected, or one whose sign-in ended, the agent shows a connect card in the Conversation and says why it needs it. The same happens when a server stops accepting your sign-in in the middle of a Turn: the Integration then shows Needs reconnecting, and the failed call becomes a connect card.

Select Connect on the card. You sign in at the server and come back to the same Conversation, where the card shows that the Integration is connected. Select Continue, and the agent goes on with the Integration’s tools. A new message works too. The Integrations selected for the Conversation don’t change. If the Integration is no longer available to you, the card says so.

What a call looks like

Each time the agent calls a tool of an Integration, the call shows as a card among the steps of its answer. The card names the Integration and the tool, for example Metabase: Run a query, and says how it went: running, done, failed or cancelled. Open the card to see the inputs the agent sent and what the Integration returned. Only you see them. The Audit Log of your admins records that a call happened, never its inputs or its result.

If you stop a Turn while a tool is running, the call is cancelled. A result that is very long is cut, and the agent is told so.

An Integration that can’t be reached

If an Integration doesn’t answer, the Turn goes on without its tools. A notice above the answer names the Integration, and the agent tells you in its answer that it couldn’t use it. Ask again later.

What the agent may change

Tools that their server declares as only reading, or as changing without destroying anything, run at once. Every other tool, including one whose server says nothing about it, pauses the Turn for your Approval before each call.

The Approval names the Integration and the tool, says what the tool does, and shows the arguments the agent wants to send. You can accept, edit the arguments as JSON and accept, or reject, exactly as for the agent’s own tools. The tool runs only after you accept; a rejected call never reaches the Integration. The Approval stays open if you reload the page or come back later, and the Turn goes on once you decide. Your admins’ Audit Log records for each call whether it needed an Approval and what you decided, never the arguments.

An Integration that is no longer available

An admin can deactivate a Tenant Integration. It then disappears from your list, and your connection to it is deleted. A Conversation that had it selected stays readable. From your next message, a notice above the agent’s answer names the Integration as no longer available, and the agent tells you if your request needed it. An Approval that was waiting for one of its tools can’t run any more. Ask your admin if you need the Integration again.