Daily ops
Webhooks: connect brasio to Zapier, Make or your own tools
Updated: 2026-06-12
Webhooks: connect brasio to Zapier, Make or your own tools
Also known as: integrations, automations, Zapier connection, Make (Integromat), n8n, event notifications.
Webhooks let brasio push events from your venue to other software the moment they happen. When a ticket is closed or a reservation comes in, brasio sends an HTTPS POST with the event data to any URL you configure — a Zapier "Catch Hook", a Make or n8n webhook trigger, or your own system.
Available events
ticket.closed— a ticket was paid and closed. Includes ticket id, ticket number, close time, total and tax (in cents), and the payment methods used.reservation.created— a booking was made on your public reservation page. Includes party size, slot time, customer name and email, and status.webhook.test— sent when you press Send test, so you can wire things up safely.
Setting up an endpoint
- Open your owner area (
yourbar.brasio.io/account) and go to Operations → Webhooks. - Press Add endpoint, paste the destination URL, and tick the events you want.
- Press Send test and check the delivery appears on the receiving side.
The URL must be public HTTPS — addresses on private networks (like 192.168.… or localhost) are rejected for security.
Each endpoint gets a signing secret (whsec_…), shown on the endpoint card.
Using it with Zapier, Make or n8n
In Zapier create a Zap starting with Webhooks by Zapier → Catch Hook, copy the hook URL it gives you, and paste it as your brasio endpoint URL. Make and n8n work the same way with their Webhook trigger modules. Press Send test in brasio and the platform will capture a sample event you can map fields from.
Verifying deliveries (optional, for developers)
Every delivery carries an X-Brasio-Signature header in the form t=<unix-time>,v1=<hex>, where v1 is the HMAC-SHA256 of "<t>.<raw body>" computed with your endpoint's signing secret. Recompute it on your side and compare; reject deliveries whose timestamp is older than a few minutes.
Retries and the delivery log
If your endpoint is down or returns an error, brasio retries up to 5 times with increasing delays. Each endpoint card shows a Deliveries log with status, HTTP response and any error, so you can see exactly what happened.
You can configure up to 10 endpoints per venue. Disabling an endpoint stops deliveries without deleting its history.
More in Daily ops
- Categories, subcategories and products
- Replace your logo
- Export and re-import the catalog (CSV / XLSX)
- Public menu PDFs
- Untappd integration: beer ratings and descriptions
- DeepL translations for menu items
- Sizes and pricing: glass, bottle, half, pint
- Wine list management
- Enable two-factor authentication
- Modifiers: optional and required
- Misc items (one-off prices)
- Per-product inventory tracking
- The container model: kegs, bottles and spirits
- Recording waste, breakage and staff drinks
- Cost prices and live GP margins
- Stocktake — counting stock by category
- Clock-in, breaks and the hours report (RDL 8/2019)
- Goods in — logging a delivery
- Stock movements log & shrinkage dashboard
- Tables and shifts: the day-to-day at the venue
- Customer profiles (CRM)
- Reservations: bookings, walk-ins and time-slot capacity
- Loyalty points: earn and redeem
- Kitchen tickets and course grouping
- Kitchen display screen (KDS)
- Browse and reprint closed tickets
- Pre-bill (cuenta provisional)
- Refunds and voids
- Discounts on a line
- Gift vouchers (gift cards)
- Cash management and end-of-service
- Till counting · cash drawer count · arqueo
- Sales report by product and size
Still stuck?
Talk to our 24/7 agent in your language. If it can't answer, we'll pass you to a human.