Connect an external API

You connect an external API to BOB so it can read and act in another system on your behalf. If the system is one of the 1,000+ apps in the integrations catalog, you connect it in a few clicks. If it is your own or a niche API, you add it as a custom connection by giving BOB the endpoint and the credentials, and it can then call that API as a tool.

Is the app already supported?

First check the integrations catalog. Most common tools (CRMs, calendars, email, spreadsheets, and more) are already there. Connecting a listed app is the fastest path and needs no API knowledge, you authorize it and BOB can use it.

How do I connect a custom or private API?

If your system is not in the catalog, connect it as a custom connection:

Have your API details ready: the base URL, the authentication (an API key or token), and which actions you want BOB to perform.
In BOB, add a custom API connection and provide those details.
Describe, in plain language, what each action does, so BOB knows when to use it.
Test it by asking BOB to perform one action, and confirm the result.

BOB uses the connection as a tool: when a job needs that system, it calls the API, reads the response, and continues the task.

Connecting through MCP

If your system exposes an MCP server (Model Context Protocol), BOB can connect to it directly and use its tools. This is the cleanest way to give BOB a rich, well-described set of actions in one step. Provide the MCP server URL and any required token.

Keep access safe

Give BOB access only to what a job needs. Every connection is a permission you granted and can revoke at any time, and you can review what BOB did through it.