Your campground runs on more than one tool. There's your booking system, perhaps a CRM, a staff chat group, a spreadsheet someone still swears by. The annoying part is keeping them in sync - manually flagging a new guest in the CRM, telling the team a big group just confirmed, copying details from one place to another.
Webhooks are how you stop doing that by hand. They let Camper BMS tell your other systems automatically when something happens, so the information flows across on its own instead of being copied over later.
What a Webhook Actually Is
In plain terms, a webhook is a message Camper BMS sends to a web address you choose, automatically, shortly after an event happens in your account. You tell Camper BMS "when a booking is confirmed, send the details here," and from then on it does exactly that - hands-off.
It's the difference between pulling and pushing. Normally a system has to keep asking "anything new yet? anything new yet?" A webhook flips that around: Camper BMS pushes the news to you soon after it happens, with the relevant details attached.
Do You Actually Need Webhooks?
Honest answer: many campgrounds never will, and that's completely fine. Camper BMS already handles bookings, invoicing, check-in and guest communications on its own. Webhooks are only for when you want to connect Camper BMS to another system that lives outside it.
You don't need to be a developer to benefit, either. Webhooks plug into no-code automation tools like Zapier, which can take a Camper BMS event and pass it on to hundreds of other apps without you writing a line of code. If you do have a developer or a custom system, they can receive the events directly. And if neither applies to you, you can safely ignore this feature - nothing depends on it.
What You Can Do With Them
Webhooks are deliberately open-ended, because the systems you might connect are up to you. You can connect Camper BMS to popular services through a no-code tool like Zapier or Make, or to a custom developer endpoint. A few of the most popular recipes:
Popular no-code integration ideas
- Automated CRM entry: when a new guest record is created, add them to your CRM automatically.
- Automatic staff alerts: when a group booking is confirmed, post a message to your team's chat or trigger an SMS to your cleaning staff.
- Arrival follow-ups: when a guest checks in, trigger a welcome email or send their arrival and access details.
- Your own dashboards: stream events into a spreadsheet or reporting tool to track arrivals, cancellations and revenue your way.
The point is that Camper BMS doesn't have to be the centre of everything - it can be a dependable source of your direct-booking data, pushing updates to the rest of your tools shortly after they happen.
The Events You Can Listen For
You choose which events each connection receives. The available events cover the moments that matter across a booking's life:
- Bookings - reserved, pending, confirmed, cancelled, or changed (a new check-in, check-out or site).
- Arrivals and departures - when a guest is checked in and when they're checked out.
- Invoices - when an invoice is paid, and when one is refunded.
- Leases - when a lease is created, activated, renewed or ended.
- Customers - when a new guest record is created.
You can subscribe a connection to every event, or narrow it down to just the handful you care about.
What's in the Data
Each webhook is a snapshot of the facts at the moment it fired. Every message includes the event name, when it happened, and which campground it relates to, plus the details specific to that event - the guest and booking for a booking event, the invoice and the guest it belongs to for an invoice event, the lease and its tenants for a lease event.
Two things worth calling out:
Consent travels with the data. Every guest in a payload carries a marketing-consent flag, so the system on the receiving end can check it before doing anything marketing-shaped. That way, your other tools know who has opted in before sending anything marketing-shaped.
The IDs are safe to share. Identifiers in the payload are public reference codes, never your internal database IDs, so you can pass them around your other tools without exposing anything sensitive.
Built to Be Secure and Reliable
Sending your booking data to another system only makes sense if it's done carefully, so webhooks have a few protections built in:
HTTPS only. Endpoints must be a secure (HTTPS) web address, so guest data is encrypted in transit.
Every message is signed. Each connection gets its own secret key, and Camper BMS uses it to digitally sign every message it sends, so your receiving system can confirm the message came from Camper BMS and was not altered in transit (as long as you keep that key confidential).
Automatic retries. If your endpoint doesn't respond, Camper BMS retries twice more over the next few minutes before recording the failure, reducing the chance of missing an event during a brief outage. If all retries fail, the event stays in the delivery log for manual replay. Each connection shows its consecutive-failure count so you can spot a broken endpoint.
A Delivery Log You Can Replay
Every delivery attempt is recorded - the event, where it went, whether it succeeded, the response, and the exact data that was sent. The Webhooks page shows your recent deliveries, and each one has a Resend button so you can re-send a payload if the other system was down when it first arrived.
Delivery records are kept for 90 days and then cleared automatically - long enough to debug and replay anything that went wrong, but not a long-term archive of guest data.
Available on Any Account
Webhooks are available on any active Camper BMS account - set up an endpoint whenever you're ready.
A Note on Consent
Webhooks aren't limited to guests who've opted in to marketing - they're for all kinds of operator workflows like CRMs, staff alerts, and internal dashboards. When you add a connection you'll tick a box confirming how the data will be used, and every payload includes a marketing-consent flag so your other tools can act on it.
How to Set One Up
Webhooks live under Integrations → Webhooks in your Camper BMS admin. Setting one up takes a minute:
- Add an endpoint - the secure (HTTPS) web address that should receive the events.
- Choose which events it should get, or leave them all selected to receive everything.
- Copy the signing secret so your receiving system can verify incoming messages.
- Hit Send test to fire a sample event and confirm the other end is receiving it.
From there, you can pause, resume or delete a connection any time. If you're connecting through a no-code tool, it'll usually walk you through pasting in the URL and secret on its side.
If you want the full technical detail - payload formats, signature verification, the complete event list - that's what our developer tools are for. And if you'd rather not touch any of this, you don't have to - it's there the day you (or your developer) want it.
Connect Camper BMS to your stack
Webhooks push your booking, invoice and lease events to whatever you use - your CRM, staff alerts, or a no-code tool like Zapier.
