Connectors

Connectors are native integrations Busy Bee maintains, OAuth in, scoped per workspace, every agent gets access.

This page is the catalog. For each connector you'll see what it unlocks, what permissions it asks for, and where to enable it.

Wiring up a connector

The flow is the same across connectors:

1. Open Settings → Integrations in your workspace.
2. Pick the service to connect.
3. Click Connect to start the OAuth handshake (or paste an API token for token-based services).
4. Authorize the requested scopes.
5. Optionally restrict the connector to specific projects or agents.

Once connected, the relevant tools appear in your agents' toolbelts automatically.

📸 Screenshot: the Integrations settings page with a list of available connectors and connection status.

GitHub

Used for any Builder-mode work and most code-touching tasks.

What agents can do: open and merge PRs, query diffs, leave review comments, push commits to branches, list repos, read files, reply to PR threads.

Scopes requested: repo read/write, PR read/write, contents read/write.

Setup notes: connect at the workspace level. Then link individual GitHub repos to projects (Settings → Repositories on each project). Pull requests opened by Busy Bee will appear authored by the connected user.

Slack

Useful for team-wide visibility and Slack-initiated work.

What agents can do: post deliverables to channels, send DMs, react to messages, monitor channels for keywords, trigger tasks from Slack messages.

Scopes requested: chat:write, channels:read, channels:history (only for channels you grant access to).

Setup notes: install the Busy Bee Slack app. Choose which channels Busy Bee can post to. Slack-initiated tasks require explicit @busy-bee mentions or a slash command.

Notion

Useful for ingesting source material and publishing drafts.

What agents can do: read pages and databases, draft new pages, append to existing pages, organize content into knowledge bases.

Scopes requested: workspace read; workspace write (write-back is optional).

Setup notes: connect at the workspace level. You'll be asked which Notion pages/databases Busy Bee can see; agents only have access to what you explicitly share.

Google Workspace

Useful for documents, sheets, and drives full of source material.

What agents can do: read Google Docs, Sheets, and Slides; export to Drive; pull files from a connected folder.

Scopes requested: Drive read; Drive write (optional).

Setup notes: connect a single Google account at the workspace level. To keep blast radius small, share only the relevant Drive folder with the connected account.

Asana

Useful for syncing tasks back to a Asana-driven workflow.

What agents can do: list tasks, create tasks, comment on tasks, change statuses, close completed work.

Scopes requested: tasks read/write, projects read.

Setup notes: connect via OAuth at the workspace level. Linking specific Asana projects to Busy Bee projects keeps the sync scoped tightly.

Email (Mailgun / SMTP)

Useful for outbound messages, drafts, notifications, reports.

What agents can do: draft and send email through a configured Mailgun domain or SMTP relay.

Scopes requested: outbound send; no inbox read.

Setup notes: configure your Mailgun domain or SMTP credentials in Settings → Email. Every send is logged; nothing goes out without an approved task.

MCP servers (custom)

If a connector you need isn't on this list, you can connect a Model Context Protocol server, your own service that speaks MCP, and Busy Bee will route tool calls to it.

Setup details for custom MCP servers are out of scope for this page; see your platform admin or get in touch.

What's next

Once your integrations are wired up, dive into Teams (Hives): the pre-built squads that put these tools to work.