Skip to main content
An incoming webhook gives any system a secure URL to push events into Hive. It is the quickest way to connect a tool Hive has no connector for — including tools with no usable API, via Zapier or Make. Hive verifies each event’s signature, then feeds it into the same sensing pipeline as every other connector.

Create a webhook

1

Open Add a connector

In Integrations → Connectors, select Add integration, then Incoming webhook — “Signed events from any system.”
2

Name it

Give it a label (up to 80 characters), for example “Ignition via Zapier”.
3

Copy the URL and the signing secret

Hive shows the webhook URL and a signing secret.
The secret is shown once. “Save your signing secret now… This is the only time the secret is shown.” Hive keeps only a sealed copy. If you lose it, delete the webhook and create a new one.
4

Send a signed event

Configure your system to POST JSON to the URL with an X-Hive-Signature header. The tile shows Awaiting events until the first valid event arrives, then Receiving.
The first incoming webhook in a workspace needs an Owner or Admin, as with enabling any provider.

What to send

  • Method: POST to https://<hive-api>/webhooks/incoming/<orgId>.<webhookId> — copy the exact URL Hive shows you.
  • Body: JSON, UTF-8, at most 64 KB.
  • Header: X-Hive-Signature — the lowercase hex HMAC-SHA256 of the raw request body, keyed with your signing secret.
Full details and code samples are in Webhook signing.

Events Hive understands natively

Hive has a built-in contract for proposal and CRM tools. A body matching one of these types is mapped straight into Business Brain facts and signals, with no AI involved:
Extra fields are ignored, so an automation that sends more than this still works. Each native event is stored on the named client in your Business Brain under these fact names, and nothing else from the body becomes a fact: See Business Brain for how facts are kept, edited and removed. Any other valid JSON is accepted too, and goes through Hive’s general ingest path.

Bridge a tool through Zapier or Make

Many proposal and practice tools — Ignition, Go Proposal, Figsflow — have no API Hive can connect to directly. Bridge them:
1

Trigger

In Zapier or Make, trigger on the tool’s event (for example “Proposal accepted”).
2

Build the body

Map the fields into the JSON above: type, entity, sourceTool, amount.
3

Sign it

Add a code step that computes the HMAC-SHA256 of the exact body you will send, and put it in X-Hive-Signature. See the Node.js and Python samples in Webhook signing.
4

POST it

Send the body to your webhook URL. A 202 response means Hive accepted it.

Responses

Replay and delete

  • Proposal events are kept as receipts, so a repeat of the same signed delivery is recognised and not processed twice.
  • Delete a webhook to stop accepting events at its URL immediately.

Webhook signing reference

Code samples in curl, Node.js and Python.

Accounting and client services

Proposal-to-client workflows.