How do I know a webhook payload really came from Briefwell?

Each webhook payload is signed, so your endpoint can verify its authenticity before processing it.

Can webhooks receive the full Report as well as Updates?

Yes. The signed webhook is one of Briefwell's full delivery channels, alongside email and Slack notifications, so it can carry both event-driven Updates and cadence-driven Reports.

Should I use a webhook if my tool isn't one of the named integrations?

Yes. The signed webhook is the general-purpose channel for delivering into any system Briefwell doesn't integrate with directly.

Deliver Briefwell updates via signed webhook

A signed webhook delivers Briefwell Updates and full Reports as JSON to any endpoint you control.

Briefwell is a proactive monitoring tool that can deliver Updates and full Reports as signed JSON to any endpoint you register. You point it at the pages, feeds, or topics to watch; when something changes, or when a scheduled brief is composed, it POSTs a signed payload to your endpoint so you can verify it and feed the data into any system you run.

Start free Book a walkthrough Watch the demo ↗

At a glance

What it does: POSTs Updates and full Reports as JSON to an endpoint you register.
Trigger: A per-change Update as it's raised, or a Report on its configured cadence.
What lands at your endpoint: A signed JSON payload carrying the source evidence — a snapshot and the record of what changed.
Security: Every payload is signed so your endpoint can verify it genuinely came from Briefwell before acting.
Setup: Register your endpoint in delivery settings, then assign it per source, bundle, or collection.
Best for: Feeding updates into any system Briefwell doesn't integrate with directly.

What the webhook channel does

The webhook channel posts Updates and full Reports as JSON to an endpoint you specify. Unlike the tool-specific destinations, it delivers the composed report data itself, and each payload is signed so your endpoint can verify it genuinely came from Briefwell before acting on it.

How to connect it

Connect a webhook once from your workspace's delivery settings by registering your endpoint, then choose it as the destination for any source, bundle, or collection.

What you get

Webhooks are the general-purpose channel: use them to feed Updates and Reports into a system Briefwell doesn't integrate with directly, and every payload carries the same source evidence — a snapshot and the record of what changed — as every other channel.

How it works

Point Briefwell at the web pages, feeds, APIs, or research topics you want to watch.
It checks them on a schedule, compares each result with the previous version, and keeps a record of what changed.
When a change matters, Briefwell creates an update — judged and explained, with the evidence attached — and delivers it to Slack, email, your CRM, or a signed webhook.

Frequently asked questions

How do I know a webhook payload really came from Briefwell?: Each webhook payload is signed, so your endpoint can verify its authenticity before processing it.
Can webhooks receive the full Report as well as Updates?: Yes. The signed webhook is one of Briefwell's full delivery channels, alongside email and Slack notifications, so it can carry both event-driven Updates and cadence-driven Reports.
Should I use a webhook if my tool isn't one of the named integrations?: Yes. The signed webhook is the general-purpose channel for delivering into any system Briefwell doesn't integrate with directly.