Integrations
An integration connects one of your other tools, such as Calendly, Kit or your own Stripe account, to your big workspace. A workspace admin pastes an API key from that tool once, big checks it works and stores it 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 keys.
What works today
This is the first release of integrations, and it is deliberately the foundation:
- Connect, test, rotate, re-verify and disconnect an integration in the dashboard, under Connect → Integrations. See Connect an integration.
- Three tools to start with, each with its own page on creating the narrowest key it allows: Calendly, Kit and Stripe.
- 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.
Reading a connected tool's data through big's MCP comes next. Today your agent can see which tools are connected and healthy; it cannot yet ask big for your upcoming Calendly bookings or a Stripe customer. 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, rotate, re-verify and disconnect, in the dashboard only. |
| Editors and viewers | See every integration and its status, last 4 characters, fingerprint and when it was last checked. The admin controls don't appear for them. |
| API tokens, the CLI and MCP | Read status only, with the integrations:read scope. |
| Anyone, including big staff | Read a saved key back: nobody can. No screen, API, CLI command or MCP tool returns one. |
Connecting, rotating and disconnecting are dashboard-only on purpose. Those actions handle a live API key, and a key typed into a CLI flag or an agent's chat would end up in shell history and transcripts. See Integration security for how keys 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.