Integrations
An integration connects one of your other tools, such as Calendly or Discord, to your big workspace. A workspace admin connects it once, either by pasting an API key from that tool or by signing in to it and approving big's read-only access. big checks it works and stores the credential encrypted, and from then on big can talk to that tool on the workspace's behalf.
The idea is simple: point your tools at big, and your own AI agent gets the context through big's MCP. Instead of wiring Claude, Cursor or whichever agent you use to five different vendors, each with its own key sitting in the agent's config, you connect the agent to big once and big holds the credentials.
What works today
This is the first release of integrations, and it is deliberately the foundation:
- Connect, test, re-verify and disconnect an integration in the dashboard, under Connect → Integrations, and rotate a pasted key or reconnect a sign-in. See Connect an integration.
- Two tools so far: Calendly and Discord connect with an API key or bot token; their pages say how to create the narrowest credential each allows. Google Drive folders link by sharing, with no credential at all, and don't count toward the limit below.
- Your agent can see what is connected. The read-only
integration_statustool on big's MCP servers,big integrations liston the CLI andGET /api/integrations/statuson the API report each integration's provider, status, and when it was last checked and used, and, for an integration whose parts are turned on one at a time, which parts are on.big integrations catalogand theintegration_catalogtool say what your workspace can connect and how many of your plan's integrations are in use. Where a workspace has a meeting integration that imports past calls, an admin's agent can also start, follow and cancel that import. - Your agent can read what connected tools brought into client records. With the
clients:readscope, it can read, read-only, the call transcripts and calendar events an integration your workspace has been set up for imported into client records, and the documents a file store keeps for the workspace. Every document read is recorded in your workspace's audit history, without the document's text.
Asking a connected tool a live question through big's MCP comes next. Today your agent can see which tools are connected and healthy, and read what they imported into client records; it cannot yet ask big for your upcoming Calendly bookings. When that arrives, it will be curated, read-only questions per tool, never an open line to the tool's whole API.
Plan limits
How many integrations a workspace can connect depends on its plan:
| Plan | Integrations |
|---|---|
| teeny (free) | 2 |
| tiny | 5 |
| big | 15 |
| bigger | 50 |
This is separate from your Instagram and Facebook account limit. Connecting Calendly never uses up a messaging slot, and connecting another Instagram account never uses up an integration. Every tool is available on every plan. Moving to a smaller plan never disconnects anything; see If you downgrade. The full plan comparison is on Plans.
Who can do what
| Who | Can |
|---|---|
| Admins and the owner | Connect, reconnect, rotate, re-verify and disconnect, in the dashboard only. Start and cancel an import of past calls from a meeting integration, in the dashboard, the CLI or MCP. |
| Editors and viewers | See every integration and its status, the connected account, a pasted key's last 4 characters and fingerprint, and when it was last checked. The admin controls don't appear for them. |
| API tokens, the CLI and MCP | Read status, with the integrations:read scope. An admin's token with meeting-sync:write can also start and cancel an import of past calls from a meeting integration. Nothing else. |
| Anyone, including big staff | Read a saved key or sign-in token back: nobody can. No screen, API, CLI command or MCP tool returns one. |
Connecting, reconnecting, rotating and disconnecting are dashboard-only on purpose. Those actions handle a live credential: a key typed into a CLI flag or an agent's chat would end up in shell history and transcripts, and signing in to a tool needs a browser. See Integration security for how credentials are stored and deleted.
An integration belongs to the workspace, not to the admin who connected it, so demoting or removing that admin doesn't disconnect it. See Team & roles.