Webhooks

Send notifications when shared resources change, or export completed meetings to your own system.

A webhook sends events from Brigg to another system automatically. Open Company settings › Webhooks to manage them. Only workspace owners and administrators can do this. Admin

Adding a webhook under Company settings › Webhooks
Adding a webhook under Company settings › Webhooks

What is sent

Under Event, choose what should trigger a delivery:

  • Resource updated is the default. It notifies your system when a published field on a shared resource changes.
  • Resource created notifies your system when a resource is created or made shared.
  • Resource deleted notifies your system when a resource is deleted or made private.
  • Meeting completed (legacy export) sends the meeting summary and the host's full private transcript, including participant details. Creating this webhook explicitly approves exporting that content to the selected endpoint. It is sent when the summary is ready, and again if the meeting is recorded again.

The three resource events use v1. They cover only the published, shared resource types you select. They contain resource identifiers and, for creation and updates, published field names, so your system can fetch the current resource through the API. They contain no field values or private resources. New resource types are never added to the subscription automatically.

Published shared records include API changes, imports and background updates. Private records, project records and internal member profiles are excluded. See the event coverage guide for details.

Creating a webhook

Under Create webhook, choose Event and enter the receiving address in Endpoint URL. It must be a publicly reachable HTTPS address. Each event can have up to three endpoints.

For a v1 event, use App to filter the published resource types. The default, All apps, shows the full list. Tick at least one resource type. Select all listed resources selects the whole list; when you filter by app, the button selects that app's resource types. Clear selection clears the types currently shown. Changing the filter keeps your selections.

Review the destination, event and selected resource types, then press Create webhook. An agent can prepare a proposal, but a person must open Review webhook proposal, check the configuration and press Approve and create before it becomes active.

After creation, save the signing secret in your receiving system and treat it like a password. Use Copy signing secret to copy it and Hide to hide it on screen.

The rules for your endpoint

  • The endpoint must answer within 10 seconds. Redirects are not followed.
  • Brigg makes up to eight attempts per delivery across approximately 24 hours.
  • For HTTP 429 and 503, Brigg respects Retry-After when it requests a longer wait.
  • After 10 deliveries in a row fail after all retries, the webhook is disabled. Enable resumes deliveries and resets the failure count.

If repeated failures disable a webhook, workspace owners and administrators receive a notice in their Brigg conversation. Repair and test the receiver, then enable the webhook. Replay retained failures and reconcile records changed while it was disabled.

In the list

Each webhook shows its address, event, version and last successful delivery. V1 webhooks also show the number of selected resource types. The list marks disabled webhooks and shows consecutive failures.

  • Copy signing secret copies the signing secret for an existing webhook.
  • Send test sends a sample event and tells you whether the endpoint accepted it. Tests do not export a real resource or meeting and do not appear in delivery history.
  • Disable / Enable stop or resume deliveries.
  • Delete removes the webhook after confirmation. Its signing secret cannot be recovered after deletion.

Delivery history

For v1 webhooks, open Delivery history · 30 days to see retained deliveries, their event, date, status, attempt count, HTTP status, error and event ID. Refresh updates the list; Load more shows older deliveries when available.

Replay sends a retained delivery again. The webhook must be enabled and the delivery must have finished. Brigg checks the current destination and access before replaying. A replay uses the same event identity, so your system must handle duplicates. History and replay are available for 30 days; the legacy meeting export has no delivery history here.

Receiving and verifying events

Open Receive and verify events for the receiver requirements. V1 signatures cover the signing timestamp and the exact request body. Your system must verify the signature, reject stale timestamps and handle duplicate or out-of-order events. The legacy meeting export keeps its original signature format.

Use Webhook documentation (English) to open the English webhook guide, with payload examples and verification instructions.