Inbound webhooks
A webhook is a secret URL that adds whatever JSON it receives to one of your app’s collections. Use it to feed an app from other tools: a Power Automate flow when someone is hired, a Zapier zap for new form entries, a nightly script, a monitoring alert. The data is simply saved, and every open page that subscribes to the collection updates live. If you’d rather check, reshape or forward what arrives, point the webhook at a server function instead.
Create one
Section titled “Create one”In the workspace open Data → Webhooks → New webhook, give it a name (“Power Automate: new hires”) and pick the collection. Copy the URL: it’s shown once.
Or from the CLI:
bunker api hooks.create hires --name "Power Automate: new hires" --collection peopleSend data
Section titled “Send data”# one recordcurl -X POST https://bunker.example.com/hooks/bkh_... \ -H 'Content-Type: application/json' -d '{"name":"Grace","team":"Platform"}'
# up to 100 records at oncecurl -X POST https://bunker.example.com/hooks/bkh_... \ -H 'Content-Type: application/json' -d '[{"name":"Linus"},{"name":"Ken"}]'
# plain HTML form posts work toocurl -X POST https://bunker.example.com/hooks/bkh_... -d 'name=Barbara&team=Design'The answer is 201 {"ok":true,"added":1,"ids":["..."]}. The records show up in Data right away, without a reload, with the webhook’s creator under “Added by”.
Send it to a function
Section titled “Send it to a function”A webhook can target one of the app’s server functions instead of a collection. In Data → Webhooks → New webhook, choose Function and pick it. Or:
bunker api hooks.create hires --name "GitHub: new issues" --function github- The JSON body (or a form post, as an object) becomes the function’s
input;ctx.triggeris{ type: 'webhook', hook }with the webhook’s name. - It runs as the person who created the webhook (or the owner, if the function is elevated), with the normal call time limit (30 s by default), since the sender is waiting for the answer.
- Whatever the function returns is sent back as the HTTP response body, as JSON. If it throws, the caller gets an error status with the message.
- It always runs the live version of the function.
export default async function (event) { if (event.action !== 'opened') return { skipped: true }; await bunker.db.collection('issues').add({ title: event.issue.title }); return { saved: true };}Rules and limits
Section titled “Rules and limits”- Records are written as the person who created the webhook, through the collection’s normal access rules. If that person loses edit access or leaves, the webhook stops working.
- Fields starting with
_are Bunker’s (_id,_author,_created…) and are ignored if sent. - 1 MB and 100 records per request, 120 requests a minute per webhook, 20 webhooks per site.
- Anyone who has the URL can add data, so treat it like a password. Delete the webhook to revoke it (
bunker api hooks.delete hires 3). - Calls are counted per webhook (last used, total records) and creating or deleting one is in the audit log.