Log your work hours automatically in Google Calendar
by
About this Applet
Create a Google Calendar event for the next guest arrival at your property. When your Webhooks URL receives a JSON event, the applet asks Beds24 for the next guest due to arrive at the specified property and adds an event to Google Calendar with arrival time and guest details. Ideal for vacation rental hosts who want arrivals logged to Google Calendar for staff or automated workflows; includes guest name, booking reference, room, and attendee email when available from Beds24.
If
Trigger ingredients
EventName
JsonPayload
OccurredAt
With
Query ingredients
BookingId
GuestFirstName
GuestLastName
Arrival
Departure
NumAdults
NumChildren
PropertyName
RoomName
Channel
Reference
Status
ArrivalTime
GuestEmail
DaysUntilArrival
Then
Action fields
Which calendar?
Start time
End time
All day?
Title
Description
Location
Attendees
Services used in this Applet
You might also like...
-
158k
-
-
Quickly create events in a Google Calendarby
133k
-
-
Get IFTTT notification for calendar birthday eventsby
82k
-
Related services
-
-
App store rating
Create your own 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.
42 triggers, queries, and actions
Any event ends
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This Trigger fires within 15 minutes of the ending time of an event on your Google Calendar. Note: The time in the ingredient will be based on the timezone set in Google Calendar.
Any event starts
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This Trigger fires a set number of minutes before the starting time of any event on your Google Calendar. Note: The time in the ingredient will be based on the timezone set in Google Calendar.
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 hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
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 hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This trigger fires when an existing booking's arrival or departure date moves.
Event from search ends
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This Trigger fires within 15 minutes of the ending time of an event on your Google Calendar that contains a specific keyword or phrase. The search looks at the event’s Title, Description, and Location. Ingredient will be based on the zone set in Google.
Event from search starts
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This Trigger fires a set number of minutes before the starting time of an event on your Calendar that contains a specific keyword or phrase in the event’s Title, Description, or Location. Ingredient will be based on the zone set in Google.
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 hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
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 hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
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 hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This trigger fires when a booking is created on one of your properties, including bookings that arrive from Airbnb, Booking.com or Vrbo.
New event added
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This Trigger fires every time a new event is added to your Google Calendar. Note: The time in the ingredient will be based on the timezone set in Google Calendar.
New event from search added
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This Trigger fires every time a new event from search is added to your Google Calendar that contains a specific keyword or phrase. The search looks at the event’s Title, Description, and Location. Ingredient will be based on the timezone set in Google
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 hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This trigger fires when a guest sends a message about one of your bookings.
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 calendar event beginnings
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 event starting times on your Google Calendar.
History of calendar event endings
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 event ending times on your Google Calendar.
History of event from search starts
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 a set number of minutes before the starting time of an event on your Google Calendar that contains a specific keyword or phrase. The search looks at the event’s Title, Description, and Location.
History of events added
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 every time a new event is added to your Google Calendar.
History of events from search added
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 every time a new event from search is added to your Google Calendar that contains a specific keyword or phrase. The search looks at the event’s Title, Description, and Location.
History of events from search ended
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 ending time (within 15 minutes) of events on your Google Calendar that contains a specific keyword or phrase. The search looks at the event’s Title, Description, and Location.
History of times you responded to a calendar invite.
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.
The query returns a list of when you responded to an event you're invited to.
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).
List Attendees
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.
Get a list of event attendees
List Busy Windows
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.
List time windows when someone is busy.
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.
Create a detailed event
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 create a detailed event in your Google Calendar.
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.
Quick add event
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 add an event to your Google Calendar. Simply include a detailed description of when and what.
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.
Any event ends
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This Trigger fires within 15 minutes of the ending time of an event on your Google Calendar. Note: The time in the ingredient will be based on the timezone set in Google Calendar.
Any event starts
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This Trigger fires a set number of minutes before the starting time of any event on your Google Calendar. Note: The time in the ingredient will be based on the timezone set in Google Calendar.
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 hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
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 hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
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.
Create a detailed event
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 create a detailed event in your Google Calendar.
Event from search ends
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This Trigger fires within 15 minutes of the ending time of an event on your Google Calendar that contains a specific keyword or phrase. The search looks at the event’s Title, Description, and Location. Ingredient will be based on the zone set in Google.
Event from search starts
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This Trigger fires a set number of minutes before the starting time of an event on your Calendar that contains a specific keyword or phrase in the event’s Title, Description, or Location. Ingredient will be based on the zone set in Google.
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 hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
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 hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This trigger fires ahead of a guest's departure, at a lead time you choose, so you can schedule the turnover.
Build an automation in seconds!
If
Select a trigger the automation will use
Any event ends
Any event starts
Booking cancelled
Booking dates changed
Event from search ends
Event from search starts
Guest checking in soon
Guest checking out soon
New booking
New event added
New event from search added
New guest message
Receive a web request
Receive a web request with a JSON payload
You respond to an event invite
Then
Select an action the automation will perform
Block off dates
Create a detailed event
Make a web request
Quick add event
Send a message to a guest
Set nightly rate
Unblock dates
You can add delays, queries, and more actions in the chat.
More on these services
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.
About Google Calendar
Google Calendar is a free time-management web application offered by Google. Turn on Applets to add the most important information, right into your calendar, automatically — and get custom notifications about the events that matter the most to you.