Get an Email Alert When Zubie Detects a Check Engine Light
2 ready-made Email 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 "Send me an email" on Email.
Automate Email and Zubie from your AI assistant
Ask OpenClaw to create Email applets for you, right from your AI assistant, with IFTTT MCP.
Set up IFTTT MCPCreate your own Email 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.
22 triggers, queries, and actions
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 5 minutes for Pro and Pro+ users, and every hour for Free users.
This Trigger fires when ANY vehicle's Check Engine light has been activated, caused by a Diagnostic Trouble Code (DTC).
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 5 minutes for Pro and Pro+ users, and every hour for Free users.
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 5 minutes for Pro and Pro+ users, and every hour for Free users.
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 5 minutes for Pro and Pro+ users, and every hour for Free users.
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 5 minutes for Pro and Pro+ users, and every hour for Free users.
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 5 minutes for Pro and Pro+ users, and every hour for Free users.
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.
Send IFTTT an email tagged
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.
Send IFTTT an email at trigger@applet.ifttt.com with a hashtag in the subject (e.g. #IFTTT) and this Trigger fires. You can optionally add a single file attachment (up to 30MB) and IFTTT will create a public URL to the file as an Ingredient.
Send IFTTT any email
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.
Send IFTTT any email at trigger@applet.ifttt.com and this Trigger fires. You can optionally add a single file attachment and IFTTT will create a public URL to the file as an Ingredient. This trigger will reject emails with attachments over 30MB.
Trip ended
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 at the end of every vehicle trip, as indicated by the Ignition being turned off.
Trip started
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 every time a vehicle starts a trip, indicated by the ignition being turned on.
Vehicle arrives at a place
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 every time a vehicle arrives at a specific place such as Home or Work (defined within Zubie).
Vehicle driven between hours
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 vehicle trip ends during a selected time frame.
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.
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.
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).
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.
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.
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 ANY vehicle's Check Engine light was been activated, caused by a Diagnostic Trouble Code (DTC).
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 a hard-acceleration event.
Send me an email
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 send you an HTML based email. Images and links are supported.
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 5 minutes for Pro and Pro+ users, and every hour for Free users.
This Trigger fires when ANY vehicle's Check Engine light has been activated, caused by a Diagnostic Trouble Code (DTC).
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 5 minutes for Pro and Pro+ users, and every hour for Free users.
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 5 minutes for Pro and Pro+ users, and every hour for Free users.
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 5 minutes for Pro and Pro+ users, and every hour for Free users.
Triggers when your vehicle is driven at speeds above a safe level (configured within Zubie).
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.
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.
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).
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.
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.
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 ANY vehicle's Check Engine light was been activated, caused by a Diagnostic Trouble Code (DTC).
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 a hard-acceleration event.
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 5 minutes for Pro and Pro+ users, and every hour for Free users.
This Trigger fires when a trip is completed that is longer than a specified distance.
Build an automation in seconds!
If
Check engine light is on for any vehicle
Then
Send me an email
You can add delays, queries, and more actions in the next step!
GET STARTED
How to connect to a Email automation
Find an Applet using Email 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!Upgrade your automations with
-
Connect to more Applets
Connect up to 20 automations with Pro, and unlimited automations with Pro+ -
Add multiple actions with exclusive services
Add real-time data and multiple actions for smarter automations -
Get access to faster speeds
Get faster updates and more actions with higher rate limits and quicker checks
More on Email and Zubie
About Email
Email and IFTTT let you automatically send yourself messages triggered by activity in your other apps.
About Zubie
Zubie and IFTTT let you automate alerts based on your vehicle's trips, driving events, and maintenance issues.