Connectors: give the AI Agent access to your other tools

Connectors let the agent read from tools outside Topo. Connect your call recorder and it can pull what was said on a call. Connect your knowledge base and it can read your internal documentation.

You will find them under Settings, on the Connectors page.

What you can connect

Call recorders. Fathom, Fireflies, Gong, Circleback, Grain, Granola, Otter and others.

Knowledge bases. Notion, Confluence, Guru, Slite, Gitbook, Coda.

Custom MCP servers. If the tool you use is not in the list but exposes an MCP server, you can add it yourself. Authentication is flexible: none, header-based, or OAuth.

Your CRM does not need a connector. HubSpot is already integrated, so the agent reads your deals, contacts and companies with no extra setup.

Connecting a tool

Pick the tool, then authorise it. You are sent to that tool’s own login to grant access, the same as for any other app, and returned to Topo when it is done.

Deciding what the agent may do

Each connector exposes a set of actions. For every one you choose whether the agent may run it on its own, or whether it should ask you first. Read-only actions are usually safe to allow. Anything that writes back to the other tool is worth keeping behind an approval.

What to use it for

The obvious one is turning calls into knowledge. Connect a call recorder, then ask the agent to read your recent calls and write up what it learned. It pulls the transcripts, extracts the useful parts, and creates a knowledge document in Topo. The same works with a knowledge base: point the agent at your existing internal docs and let it bring them across.

Good to know

• Access is granted per tool, and you can revoke it from that tool whenever you want.

• If a connector stops working, the usual cause is an expired or revoked authorisation. Reconnect it from the Connectors page.