Webhooks let LetPilot trigger actions in any external tool the moment something happens - a new booking, a task completed, a check-in.
A webhook is a notification that one piece of software sends to another the moment something happens. When a new booking is confirmed in LetPilot, a webhook can instantly notify your accounting software, update a Google Sheet, post a message in your team Slack channel, or trigger any other automated action you have configured.
Unlike API polling — where your system repeatedly asks "has anything changed?" — webhooks push information in real time. The moment an event occurs, the notification fires. For a holiday rental operator, this means your connected tools know about new bookings, cancellations, and task completions as fast as LetPilot does.
Without webhooks, connecting your property management system to other tools requires either manual data re-entry (time-consuming and error-prone) or custom API integrations (expensive and requires developer skills).
Webhooks combined with a connector like Zapier or Make give non-technical operators the ability to build sophisticated automations without writing a line of code. Any tool that accepts a webhook can be part of your automated workflow.
LetPilot sends HMAC-signed webhook notifications for all major platform events. HMAC signing means the receiving system can verify that the webhook genuinely came from LetPilot and was not tampered with in transit — important for security if your webhook triggers sensitive actions.
Events LetPilot sends webhooks for include: booking confirmed, booking cancelled, booking modified (dates, guests, price), booking payment received, inquiry received, check-in (guest arrival day), check-out (guest departure day), task created, task completed, guest message received, noise alert triggered, and review received.
Each webhook payload contains the full context of the event — booking details, property information, guest data — so the receiving system has everything it needs to act without making additional API calls.
Zapier is the most accessible tool for connecting webhooks to other services. Here is a practical walkthrough using a new booking notification as the example.
Create a new Zap in Zapier. Set the trigger to Webhooks by Zapier and choose Catch Hook. Zapier provides a unique webhook URL for this Zap.
In LetPilot webhook settings, add a new webhook endpoint. Paste the Zapier URL and select which events should trigger this webhook. For this example, select Booking confirmed.
Make a test booking in LetPilot. Zapier receives the webhook payload and shows you the data structure. This is how Zapier learns the structure for the subsequent action step.
Now choose what Zapier does with the information. For example: Google Sheets — add a row to a bookings log spreadsheet with booking reference, property, guest name, dates, and value. Slack — send a message to your team channel: "New booking at [Property Name]: [Guest Name], [Check-in] to [Check-out], £[Total]". Gmail — send a custom notification email to a co-host or property manager. Notion or Airtable — create a record in your operations database.
Activate the Zap and monitor the first few live events to confirm everything is working correctly.
New booking to Slack alert: notify your team the moment a booking is confirmed. Include property name, dates, number of guests, and booking source so everyone is immediately aware without needing to check LetPilot.
Check-in day to property manager SMS: send an SMS to the relevant property manager on the morning of a check-in with the guest arrival time and any special notes from the booking. This replaces a manual morning briefing.
Task completed to photo archive: when a cleaning task is marked complete with photo evidence in LetPilot, automatically save the photos to a Google Drive folder organised by property and date. Creates an ongoing visual record of property condition.
New inquiry to CRM contact: when a guest submits an inquiry, create a contact record in HubSpot or Pipedrive so you can track your sales pipeline for direct booking conversion.
Booking payment received to accounting entry: for custom accounting flows, create a transaction record in your system of choice the moment a payment is confirmed.
Noise alert to automated guest message: when LetPilot receives a noise alert from Minut, automatically send the relevant guest a polite reminder about house rules without needing to manually intervene.
If you are building a custom webhook receiver rather than using Zapier or Make, you should verify the HMAC signature on every incoming webhook. LetPilot includes a signature in the X-LetPilot-Signature header of each request.
Verification prevents malicious actors from sending fake webhooks to your endpoint to trigger unintended actions. The verification process: extract the signature from the header, compute the expected HMAC-SHA256 of the raw request body using your webhook secret key, and compare the computed signature to the received signature. Only process the webhook if they match. LetPilot documentation includes code samples for PHP, Node.js, and Python.
Make (formerly Integromat) offers more sophisticated workflow logic than Zapier, including conditional branches, data transformations, and multi-step sequences. For complex automations — sending different notifications depending on the booking source or applying different logic per property — Make visual workflow builder is more powerful.
The principles are identical: configure LetPilot to send webhooks to your Make webhook URL, then build your scenario in Make with whatever branching logic your operation requires.
If webhooks are new to you, start with one automation that solves an actual problem in your workflow. The most common starting point is a new booking notification to a Slack or WhatsApp channel — immediately useful, easy to set up, and gives you confidence to build more complex automations from there. Once you see the pattern, the possibilities expand quickly.