Skip to main content
Hive is designed to plug into the systems you already run. Most teams never write code: they connect tools with OAuth, build workflows in the builder, and configure agents in Agent Studio. When you do want to build something custom, this page maps the ways in that exist today.
Hive does not currently offer a general customer REST API with personal API keys, or outgoing webhooks. The product’s own API is authenticated with signed-in user sessions and is not a supported integration surface. If you need programmatic access that the options below do not cover, tell us what you are building.

​
What you can build with today

Incoming webhooks

Push signed JSON events from any system into Hive — ideal for tools without a native connector, or bridges from Zapier or Make.

Public workflow forms

Start a deployed workflow from your website or another system by submitting its public form.

MCP servers

Connect any Model Context Protocol server over HTTPS and let Hive use its tools, under approval.

Workflow export and import

Export a workflow as JSON, keep it in version control, and import it into another workspace.

​
Incoming webhooks: send data into Hive

Create a webhook in Integrations → Add integration → Incoming webhook. Hive gives you a unique URL and a signing secret, shown once. Your system sends JSON with an X-Hive-Signature header — a hex HMAC-SHA256 of the raw body — and Hive acknowledges with 202.
  • Typed business events (proposal.created, proposal.won, client.created) feed Hive’s certified sources and signals.
  • Any other valid JSON is still accepted and ingested as a generic event.
  • Duplicate deliveries are recognised and acknowledged without being processed twice.
Signing examples in several languages are in Webhook signing.

​
Public workflow forms: start work from outside Hive

A workflow with a Public form trigger has a link anyone can submit, without signing in. Behind that link is a small, rate-limited HTTP interface you can call yourself — for example from a contact form on your website — with an idempotency key so retries never start a second run. See Public form API.

​
MCP servers: bring your own tools

Hive is an MCP client. Connect a curated server (Notion, Linear, Sentry, Stripe) in one click, or any Streamable HTTP MCP server by URL with no auth, a bearer token, or OAuth 2.1. Hive discovers the tools, pins a fingerprint of each one, and treats them as high-risk actions that go through approval. See MCP servers.
Hive does not expose its own MCP server today.

​
Workflow export and import: workflows as code

Every workflow can be exported as a versioned JSON document and imported again as a private draft. Import checks the graph against the same rules as deploy and lists up to 50 of the issues it finds, and personal account ids are stripped on export. See Workflow export format.

​
Connectors

For the systems most businesses run — accounting, payments, CRM, support, email, calendars, files and developer tools — use a built-in connector rather than building your own.

​
What does not exist yet

​
Limits at a glance

The complete list is in Limits reference.

How Hive works

The architecture behind these surfaces.

Webhook signing

Code samples for signed webhooks.

Security overview

How Hive keeps integrations safe.

Integrations overview

Every way to connect a tool.