Close menu
Explore Plans
Mobile menu Close menu
Back

AduroSmart to Zubie integrations

Automate your workflows between AduroSmart and Zubie with IFTTT.

Create your own AduroSmart 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.

33 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).

Contact switch sensor closed

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 contact switch sensor closed.

Contact switch sensor opened

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 contact switch sensor opened.

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.

Motion sensor 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.
This trigger fires motion sensor detected

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).

History of contact switch sensor closed

Pro plus icon
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 contact switch sensor closed.

History of instances a vehicle left a place

Pro plus icon
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 motion sensor detected

Pro plus icon
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 motion sensor detected.

History of trip ends

Pro plus icon
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

Pro plus icon
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

Pro plus icon
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

Pro plus icon
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.

History of when Check engine light was on for any vehicle

Pro plus icon
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).

History of when hard acceleration was detected

Pro plus icon
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.

Activate a scene

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 activate a scene on your lights. You must make sure your AduroSmart connected.

Change color

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 change the color of your lights. Default to white if no color match is found.

Dim device

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 dim your device.

Identify device

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 identify your device.

Toggle device on/off

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 toggle your device on or off.

Turn off color loop

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 turn off color loop for your lights.

Turn off device

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 turn off your device.

Turn on color loop

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 turn on a color loop effect for your color lights.

Turn on device

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 turn on your device.

Activate a scene

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 activate a scene on your lights. You must make sure your AduroSmart connected.

Change color

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 change the color of your lights. Default to white if no color match is found.

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).

Contact switch sensor closed

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 contact switch sensor closed.

Contact switch sensor opened

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 contact switch sensor opened.

Dim device

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 dim your device.

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).

History of contact switch sensor closed

Pro plus icon
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 contact switch sensor closed.

History of instances a vehicle left a place

Pro plus icon
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 motion sensor detected

Pro plus icon
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 motion sensor detected.

Build an automation in seconds!

You can add delays, queries, and more actions in the next step!

GET STARTED

How to connect to a AduroSmart automation

Find an automation using AduroSmart

Find an automation to connect to, or create your own!

Connect IFTTT to your AduroSmart account

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!
Get started

Upgrade your automations with

Start your free trial

More on AduroSmart and Zubie

About AduroSmart

AduroSmart connected bulbs and smart gateway let you to take full control of your lighting, sockets, dimmers, switches. 

Connect AduroSmart

More integrations with AduroSmart

About Zubie

Zubie is a connected car service that makes driving safer, easier and less expensive. It tracks your trips, alerts you to engine and battery problems, unsafe driving events, arrivals and departures, and more.

Connect Zubie

More integrations with Zubie