Add completed Zubie trips to Google Calendar
by
1 ready-made Google Calendar and Zubie Applets
Turn one on, or build your own. Zubie can start an automation with "Check engine light is on for any vehicle", and IFTTT can then run "Create a detailed event" on Google Calendar.
Automate Google Calendar and Zubie from your AI assistant
Ask OpenClaw to create Google Calendar applets for you, right from your AI assistant, with IFTTT MCP.
Set up IFTTT MCP
Create your own Google Calendar and Zubie 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.
41 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.
Check engine light is on for any vehicle
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 ANY vehicle's Check Engine light has been activated, caused by a Diagnostic Trouble Code (DTC).
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.
Hard acceleration detected
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+.
Triggers when your vehicle has a hard-acceleration event.
Hard braking detected
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+.
Triggers when a vehicle detects a hard brake event.
High speed driving detected
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+.
Triggers when your vehicle is driven at speeds above a safe level (configured within Zubie).
Long-distance trip
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 trip is completed that is longer than a specified distance.
Low battery condition for any vehicle
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 battery levels fall below normal levels for any vehicle in your account. The vehicle ingredient specifies the name of the vehicle with the problem.
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
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 instances a vehicle left a place
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 instances when a vehicle left a place.
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 trip ends
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 the end of every vehicle trip, as indicated by the Ignition being turned off.
History of vehicle arriving at a place
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 when a vehicle arrived at a specific place such as Home or Work (defined within Zubie).
History of vehicle driven between hours
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 when a vehicle trip ends during a selected time frame.
History of vehicle out of range
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 when your vehicle was further than an allowed distance from a specified location.
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.
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.
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.
Check engine light is on for any vehicle
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 ANY vehicle's Check Engine light has been activated, caused by a Diagnostic Trouble Code (DTC).
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.
Hard acceleration detected
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+.
Triggers when your vehicle has a hard-acceleration event.
Hard braking detected
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+.
Triggers when a vehicle detects a hard brake event.
High speed driving detected
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+.
Triggers when your vehicle is driven at speeds above a safe level (configured within Zubie).
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.
Build an automation in seconds!
If
Select a trigger the automation will use
Any event ends
Any event starts
Check engine light is on for any vehicle
Event from search ends
Event from search starts
Hard acceleration detected
Hard braking detected
High speed driving detected
Long-distance trip
Low battery condition for any vehicle
New event added
New event from search added
Trip ended
Trip started
Vehicle arrives at a place
Vehicle driven between hours
Vehicle leaves a place
Vehicle out of range
You respond to an event invite
Then
Select an action the automation will perform
Create a detailed event
Quick add event
You can add delays, queries, and more actions in the chat.
GET STARTED
How to connect to a Google Calendar automation
Find an Applet using Google Calendar and Zubie
Find an automation to connect to, or create your own!Connect IFTTT to your accounts
Securely connect the Applet services to your respective accounts.Finalize and customize your Applet
Review trigger and action settings, and click connect. Simple as that!Make more happen with your credits
-
More credits, more possibilities
Get more credits per month to power more automation activity. -
Power more advanced automations
Use credits to power your automations, including actions that require more processing. -
Access faster speeds and higher rate limits
Get faster updates and more actions with increased rate limits and more frequent checks.
Google Calendar and Zubie tips, tools, and resources
More on Google Calendar and Zubie
About Google Calendar
Google Calendar and IFTTT let you trigger automations when calendar events happen, and create new events automatically.
About Zubie
Zubie and IFTTT let you automate actions based on your vehicle's location, driving behavior, and maintenance alerts.