Connectors¶
The 24 systems BotBoss can connect to, how each one is authenticated, and what an agent can do through it once connected. Generated from the connector registry itself, so it cannot drift from what the product actually supports.
Read this table as the answer to four questions: what can I connect, how do I connect it, can agents write through it or only read, and which permission has to be granted before they can.
| Connector | How you connect it | Scope of a connection | Agent access | What gates that access | Credential independently bounded? |
|---|---|---|---|---|---|
| BambooHR | Paste a long-lived vendor token — no expiry, no rotation | one per workspace | data sync only — no agent tools | — | n/a — no agent-facing tools |
| Bill.com | Sign in with your vendor username, password and org | one per workspace | data sync only — no agent tools | — | n/a — no agent-facing tools |
| Box | Sign in with the vendor (OAuth, using the BotBoss app) Sign in with the vendor (OAuth, using your own registered app) |
one per workspace | via the vendor's own MCP | granted per workspace connection; scoped by the vendor at sign-in | ask your workspace admin |
| Brex | Paste a long-lived vendor token — no expiry, no rotation | one per workspace | read (17) | granted per workspace connection; scopes: data:read |
ask your workspace admin |
| Hosted browser | Nothing to connect — BotBoss supplies the vendor credential | several per workspace | data sync only — no agent tools | — | n/a — no agent-facing tools |
| Dropbox | Sign in with the vendor (OAuth, using the BotBoss app) Sign in with the vendor (OAuth, using your own registered app) |
one per workspace | data sync only — no agent tools | — | n/a — no agent-facing tools |
| Inbound Email | BotBoss generates a secret that you give to the vendor (inbound only) | several per workspace | data sync only — no agent tools | — | n/a — no agent-facing tools |
| Expensify | Paste an account id + secret, sent in the request body on every call | one per workspace | data sync only — no agent tools | — | n/a — no agent-facing tools |
| Google Drive | Sign in with the vendor (OAuth, using the BotBoss app) Sign in with the vendor (OAuth, using your own registered app) |
one per workspace | read (5) | granted per workspace connection | yes — a vendor scope fixed when the workspace connected, narrower than the connector's full surface |
| Gmail | Sign in with the vendor (OAuth, using the BotBoss app) Sign in with the vendor (OAuth, using your own registered app) |
one per user | read (5) + write (6) | granted per workspace connection; 3 of 6 write tools off unless enabled for the deployment | yes — a vendor scope fixed when the workspace connected, narrower than the connector's full surface |
| Gusto | Connect the vendor's hosted MCP endpoint (sign-in + PKCE) | one per workspace | data sync only — no agent tools | — | yes — a vendor scope fixed when the workspace connected, narrower than the connector's full surface |
| HubSpot | Sign in with the vendor (OAuth, using the BotBoss app) Sign in with the vendor (OAuth, using your own registered app) Paste a long-lived vendor token — no expiry, no rotation |
one per workspace | read (11) + write (5) — money semantics not yet catalogued (5 of 5) | granted per workspace connection; write tools off unless enabled for the deployment | yes — a pasted token whose vendor-reported scope is verified against the grant |
| NetSuite | Paste an OAuth client id, certificate id and the matching private key; short-lived tokens are minted from them | one per workspace | data sync only — no agent tools | — | n/a — no agent-facing tools |
| Notion | Connect the vendor's hosted MCP endpoint (sign-in + PKCE) Sign in with the vendor (OAuth, using the BotBoss app) connects in two halves: the agent half (live tool access), the sync half (warehouse extract) |
one per workspace | data sync only — no agent tools | — | yes — a vendor scope fixed when the workspace connected, narrower than the connector's full surface |
| Outlook | Sign in with the vendor (OAuth, using the BotBoss app) Sign in with the vendor (OAuth, using your own registered app) |
one per user | via the vendor's own MCP | granted per workspace connection; scoped by the vendor at sign-in | ask your workspace admin |
| Plaid | Choose your institution in the vendor's own consent widget | several per workspace | read (3) + write (1) — money semantics not yet catalogued (1 of 1) | granted per workspace connection; write tools gated by the connection grant only | yes — a vendor scope fixed when the workspace connected, narrower than the connector's full surface |
| QuickBooks Online | Sign in with the vendor (OAuth, using the BotBoss app) Sign in with the vendor (OAuth, using your own registered app) Paste your own OAuth app's client id + secret and a refresh token you already minted against it |
one per workspace | read (7) + write (8) — ⚠ 1 irreversible — money semantics not yet catalogued (3 of 8) | granted per workspace connection; 5 of 8 write tools off unless enabled for the deployment | ask your workspace admin |
| Ramp | Paste an OAuth client id + secret; short-lived tokens are minted from it | one per workspace | read (21) + write (5) — money semantics not yet catalogued (2 of 5) | granted per workspace connection; write tools off unless enabled for the deployment | yes — a vendor credential scope minted fresh from this workspace's grant |
| REST API | Paste a long-lived vendor token — no expiry, no rotation | several per workspace | data sync only — no agent tools | — | n/a — no agent-facing tools |
| Salesforce | Sign in with the vendor (OAuth, using the BotBoss app) Sign in with the vendor (OAuth, using your own registered app) |
one per workspace | read (4) + write (2) | granted per workspace connection; write tools off unless enabled for the deployment | yes — a vendor scope fixed when the workspace connected, narrower than the connector's full surface |
| SharePoint / OneDrive | Sign in with the vendor (OAuth, using the BotBoss app) Sign in with the vendor (OAuth, using your own registered app) Paste your own OAuth app's client id + secret and a refresh token you already minted against it |
one per workspace | data sync only — no agent tools | — | n/a — no agent-facing tools |
| Stripe | Sign in with the vendor (OAuth, using the BotBoss app) Sign in with the vendor (OAuth, using your own registered app) Paste a long-lived vendor token — no expiry, no rotation |
one per workspace | read (12) | granted per workspace connection; scopes: data:read |
n/a — no agent-facing tools |
| Twilio | Paste an account id + secret, sent as HTTP Basic on every call | one per workspace | data sync only — no agent tools | — | n/a — no agent-facing tools |
| Xero | Sign in with the vendor (OAuth, using the BotBoss app) | one per workspace | data sync only — no agent tools | — | n/a — no agent-facing tools |
How to read agent access¶
A connection existing does not mean an agent can use it. Every tool declares whether it reads or writes, and the permission it requires; an agent only gets a tool if that permission has been granted to it. read (12) + write (3) means twelve tools that only look and three that change something in the vendor system — and the write tools stay unavailable until a write permission is granted.
Read/write is declared by each tool, never guessed from its name — a CI guard rejects any tool that does not declare it.
Connecting an account is not the same as letting an agent change things in it. Every connection is granted per workspace, and most connectors additionally withhold their write tools until those are enabled for the deployment — the table says which, per connector, because it is not uniform.
Credential independently bounded? answers a different question: if every check above were bypassed, would the vendor credential itself still refuse the call? A workspace grant and an env flag are things our code enforces; this column states what the vendor's own permissions system enforces, if anything. Where it reads ⚠, nothing does — the credential could reach the connector's whole surface on its own.
The individual tool names for each connector are not listed on this public page. See Agent tools for the platform tool reference, or ask your workspace admin for the connector detail.