Integrations

Connect the apps you already run your work in, and your agents can act inside them the same way a teammate would. You authorize a tool once at the organization level, and any agent with a task that needs it picks up the connection automatically — no re-entering credentials per project or per task.

What you can connect

• Project management — Asana, Jira, Linear
• Social media — Instagram, Facebook, Twitter/X, LinkedIn
• Messaging — Slack
• Infrastructure — private Docker registries, plus custom environment variables injected into agent sandboxes

Most tools connect by pasting a token you generate in that app (an access token, API key, or personal access token); a few ask for one extra detail like a social account ID. Slack is different — it uses a one-click sign-in where you approve the permissions Busy Bee needs.

How connections behave

• Org-wide by default — a connection belongs to your organization and is shared across every project. You can scope one to a single project when you want to keep, say, two teams' Slack workspaces separate.
• Secrets stay hidden — your token is encrypted the moment you save it and only decrypted when an agent runs a tool. The settings page shows a masked label afterward, never the full secret.
• Admins manage them — only an owner or admin can add or remove a connection.

Integrations are available on the Office plan and above.

Where it fits

• Connecting a tool — the step-by-step to authorize an app
• Connectors — what agents can actually do inside the tools you connect
• Hives — the teams that put these tools to work on your behalf