If a webhook is triggered, get a mobile notification
About this Applet
Send Beds24 booking details to a webhook to notify external systems. It runs when a new booking is created on one of your Beds24 properties and makes a web request to the URL you provide via Webhooks. This is useful for property managers who want to forward bookings from Beds24 to CRMs, PMS tools, analytics, or custom endpoints via Webhooks. Note: This requires a reachable webhook endpoint (URL).
If
Trigger ingredients
BookingId
GuestFirstName
GuestLastName
Arrival
Departure
NumAdults
NumChildren
PropertyName
RoomName
Channel
Reference
Status
BookingTime
Then
Action fields
url
method
content_type
additional_headers
body
You might also like...
-
544
-
-
Relay a Webhooks request to another URL
276
-
-
Add Webhooks data to Google Sheets automatically
256
-
Related services
-
-
App store rating
Create your own Webhooks and Beds24 workflow
Create custom workflows effortlessly by selecting triggers, queries, and actions. With IFTTT, it's simple: “If this” trigger happens, “then that” action follows. Streamline tasks and save time with automated workflows that work for you.
20 triggers, queries, and actions
Booking cancelled
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when a booking on one of your properties is cancelled, so you can free up the dates and stand down the turnover.
Booking dates changed
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when an existing booking's arrival or departure date moves.
Guest checking in soon
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires ahead of a guest's arrival, at a lead time you choose, so you can send the check-in details and get the property ready.
Guest checking out soon
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires ahead of a guest's departure, at a lead time you choose, so you can schedule the turnover.
New booking
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when a booking is created on one of your properties, including bookings that arrive from Airbnb, Booking.com or Vrbo.
New guest message
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when a guest sends a message about one of your bookings.
Receive a web request
Realtime trigger
Realtime Applets run after the trigger service notifies IFTTT of a new trigger event. Since IFTTT is notified proactively of new trigger events, realtime Applets normally run within a few seconds of a trigger event occurring.
This trigger fires every time the Webhooks service receives a web request to notify it of an event. To find your webhook URL and key, open Documentation on the Webhooks service page (mobile: Account > My services > Webhooks).
Receive a web request with a JSON payload
Realtime trigger
Realtime Applets run after the trigger service notifies IFTTT of a new trigger event. Since IFTTT is notified proactively of new trigger events, realtime Applets normally run within a few seconds of a trigger event occurring.
This trigger fires every time the Webhooks service receives a web request to notify it of an event. To find your webhook URL and key, open Documentation on the Webhooks service page (mobile: Account > My services > Webhooks).
Check availability
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query finds out whether a property is free for the dates and guest count you give it, and what it would cost.
Find a booking by guest
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query finds a booking from a guest's name, email address or booking reference.
History of web requests received
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of times the Webhooks service received a web request to notify it of an event. To find your webhook URL and key, open Documentation on the Webhooks service page (mobile: Account > My services > Webhooks).
Make a web request
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns the status code from a request made to the provided URL. If the response body is in the correct format it will also return the body’s extracted values. Please see the documentation link on the Webhooks service page.
Make a web request with JSON response
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns the JSON response body. You can use filter code to parse it. Please see the documentation link on the Webhooks service page.
Next arrival at a property
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns the next guest due to arrive at a property, and when.
Rate and availability for a date
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns what a room costs on a given date and whether that date can still be booked.
Block off dates
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action marks a date range as unavailable on a room, and Beds24 pushes the block out to every channel the room is listed on.
Make a web request
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will make a web request to a publicly accessible URL. NOTE: Requests may be rate limited.
Send a message to a guest
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action sends a message to the guest on one of your bookings.
Set nightly rate
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action sets the nightly price for a room over a date range, and Beds24 pushes the new price to every channel the room is listed on.
Unblock dates
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action removes a block from a date range on a room, putting it back on sale everywhere it is listed.
Block off dates
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action marks a date range as unavailable on a room, and Beds24 pushes the block out to every channel the room is listed on.
Booking cancelled
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when a booking on one of your properties is cancelled, so you can free up the dates and stand down the turnover.
Booking dates changed
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when an existing booking's arrival or departure date moves.
Check availability
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query finds out whether a property is free for the dates and guest count you give it, and what it would cost.
Find a booking by guest
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query finds a booking from a guest's name, email address or booking reference.
Guest checking in soon
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires ahead of a guest's arrival, at a lead time you choose, so you can send the check-in details and get the property ready.
Guest checking out soon
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires ahead of a guest's departure, at a lead time you choose, so you can schedule the turnover.
History of web requests received
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of times the Webhooks service received a web request to notify it of an event. To find your webhook URL and key, open Documentation on the Webhooks service page (mobile: Account > My services > Webhooks).
Make a web request
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns the status code from a request made to the provided URL. If the response body is in the correct format it will also return the body’s extracted values. Please see the documentation link on the Webhooks service page.
Make a web request
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will make a web request to a publicly accessible URL. NOTE: Requests may be rate limited.
Make a web request with JSON response
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns the JSON response body. You can use filter code to parse it. Please see the documentation link on the Webhooks service page.
New booking
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when a booking is created on one of your properties, including bookings that arrive from Airbnb, Booking.com or Vrbo.
Build an automation in seconds!
If
Select a trigger the automation will use
Booking cancelled
Booking dates changed
Guest checking in soon
Guest checking out soon
New booking
New guest message
Receive a web request
Receive a web request with a JSON payload
Then
Select an action the automation will perform
Block off dates
Make a web request
Send a message to a guest
Set nightly rate
Unblock dates
You can add delays, queries, and more actions in the chat.
More on Webhooks and Beds24
About Webhooks
Learn to use webhooks and integrate other services on IFTTT with your DIY projects. You can create Applets that work with any device or app that can make or receive a web request. If you'd like to build your own service and Applets, check out the IFTTT Developer Dashboard. Connect a webhook to any of the 1000+ apps and services on IFTTT.
About Beds24
Beds24 is all-in-one property management and channel management software for short-term rentals, hotels, B&Bs, hostels and campgrounds. It syncs bookings, rates and availability across 60+ booking platforms including Airbnb, Booking.com and Vrbo, and adds a direct booking engine, payment processing, guest communication and automation for professional property managers in over 150 countries.