Who can set up webhooks
Owners and admins. A webhook can only include events from modules you can read. A company can have up to 10 webhooks.
A webhook works as the person who set it up. It sends only events they can still read: if their role changes so they can’t, or they leave the company, it stops sending them. Someone who can read them turns the webhook off and on again to take it over.
Add a webhook
- Go to Settings › Webhooks.
- Choose Add Webhook.
- Enter the URL. It must be a public
https://address. Private addresses and redirects are refused. - Enter a Secret of at least 16 characters. BizGen uses it to sign every message. Keep your own copy: BizGen stores it encrypted and never shows it again.
- Under Events, tick the events you want.
- Choose Add Webhook.
You can’t edit a webhook. To change its address, events or secret, delete it and add it again.
The events
invoice.updated is sent when an invoice is edited, sent, cancelled, or a payment or credit note changes what is paid. quotation.updated is sent when a quotation is edited, sent, answered by the client, or turned into an invoice.
client.created,client.updatedproject.created,project.updatedquotation.created,quotation.updatedinvoice.created,invoice.updatedpayment.createdclaim.submitted,claim.approved,claim.rejected,claim.paid
Each message is a POST with a JSON body:
{ "event": "invoice.created", "timestamp": "2026-10-18T03:15:00.000Z", "data": { ... } }
data is the record as it was saved. The request also carries these headers:
X-Webhook-Event: the event name;X-Webhook-Id: the delivery’s ID;X-Webhook-Timestamp: when it was sent, in seconds since 1970 (Unix time);X-Webhook-Signature:sha256=followed by the signature.
Check the signature
The signature is an HMAC-SHA256, keyed with your secret and written in hex, of the timestamp, a full stop, and the raw request body. Compute it over the body exactly as received, before parsing the JSON:
const crypto = require("node:crypto");
function isFromBizGen(rawBody, headers, secret) {
const timestamp = headers["x-webhook-timestamp"] || "";
// Refuse a message more than 5 minutes old: it may be an old one sent again.
if (Math.abs(Date.now() / 1000 - Number(timestamp)) > 300) return false;
const expected =
"sha256=" + crypto.createHmac("sha256", secret).update(`${timestamp}.${rawBody}`).digest("hex");
const a = Buffer.from(expected);
const b = Buffer.from(headers["x-webhook-signature"] || "");
return a.length === b.length && crypto.timingSafeEqual(a, b);
}
Reject the message if this returns false. A retry is signed again with its own time.
Answer and retries
Reply with any 2xx status within 10 seconds. BizGen sends each message at least once, so the same message can arrive twice: skip any X-Webhook-Id you have already handled.
If your server times out, can’t be reached, or answers 408, 429 or 5xx, BizGen tries again after about 30 seconds, then 1, 2 and 4 minutes. After 5 failed attempts it gives up. Any other 3xx or 4xx answer fails the delivery at once, without retries.
Delivery history
Delivery history on the same page lists the latest deliveries, newest first, 25 at a time. Each shows the event, its status (pending, processing, delivered, failed or cancelled), the number of attempts, your server’s last HTTP status, any error, and its ID. Use Previous deliveries and Next deliveries to page through.
Pause or delete a webhook
- To pause, turn off the switch next to the webhook. Nothing is sent while it is off, and deliveries still waiting are cancelled when they come due. Events that happen while it is off are not sent later.
- To delete, choose the bin icon, then Delete webhook. Deliveries still waiting are dropped. Past delivery history is kept.