Skip to main content
Hive works on top of the systems your team already uses. You connect a tool once, Hive reads what you allow, and everything it notices or proposes stays tied to the source it came from. Nothing is migrated: your data stays where it is, and Hive reads it in place. Open Integrations in the sidebar. The screen has two tabs:
  • Connectors — “Connectors let Hive read the tools you already run and carry out approved actions.”
  • Channels — “Ask Hive from Slack or Microsoft Teams. Signals and approvals stay in Hive.”

​
Four ways to connect

Managed OAuth connectors

Sign in to a provider such as Xero, HubSpot, Gmail or GitHub. Hive holds the credentials in its vault and starts read-only.

MCP servers

Connect an official vendor MCP server (Notion, Linear, Sentry, Stripe) or any Model Context Protocol server by URL.

Incoming webhooks

Let any system push signed JSON events into Hive, directly or through Zapier or Make.

Slack and Teams channels

Ask Hive questions from Slack or Microsoft Teams with an @mention or a DM.
A connector brings data in and, with approval, carries actions out to that tool. A channel is only a place to talk to Hive — it never delivers signals or approvals.

​
What Hive does with a connected tool

Once a tool is connected, Hive uses it in several ways at once:

​
Read-first, by design

Every new account starts at the Read level: Hive can search and summarise, and nothing leaves Hive. You can raise an account to Draft (Hive prepares actions and you approve them) or Act (Hive carries out actions that policy has already approved). Today every write to a connected tool is routed to human approval regardless of level. See Accounts and autonomy.
Connecting a tool never, on its own, gives Hive permission to change anything in it.

​
Who can connect what

  • An Owner or Admin enables a provider for the workspace, simply by connecting it first.
  • After that, any member can connect their own account of that provider. Before a provider is enabled, members see: “A workspace administrator must enable this provider before you can connect a personal account.”
  • Every connection belongs to the member who made it. Owners and Admins see a Workspace connections panel with metadata only — personal credentials, configuration, scopes, webhook URLs and actions stay private to their owner.
  • Channels (Slack, Teams) and account autonomy levels are managed by Owners and Admins.

​
How fresh the data is

  • Right after you connect, Hive runs a first sync straight away.
  • After that, Hive’s always-on loop collects from every live connector hourly.
  • Some providers also forward realtime events to Hive, which are picked up as they arrive.
  • An Admin can press Run loop now on the Signals page or on the Connectors tab to refresh immediately.

​
What is in the catalog

Hive’s catalog covers accounting, payments, CRM, support, email, calendar, files, project tracking and developer tools. The tiles you see depend on how your Hive workspace is configured, and some providers are connect-only while their reads and actions are being built. The full list, with what each provider supports today, is in the integrations catalog.

​
Build your own connector

If the tool you need is not in the catalog:
  • If it has an MCP server, connect it by URL — see MCP servers.
  • If it can send webhooks (or you use Zapier or Make), point it at a signed incoming webhook.
The Built by me filter on the Connectors tab shows the MCP servers and webhooks you created.
Hive does not offer customer API keys or outgoing webhooks today. See the developer overview for what you can build against.

Connect an app

Step-by-step: connect your first tool.

Integrations catalog

Every provider and what it supports.

Health and disconnecting

Connection statuses and what disconnecting does.

Security overview

How credentials and data are protected.