Close menu
Explore Plans
Mobile menu Close menu
Back

Smitch to Zubie integrations

Automate your workflows between Smitch and Zubie with IFTTT.

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

47 triggers, queries, and actions

A motion 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 when a motion detected

A sound 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 when a sound is detected

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.

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.

Get list of notifications

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.
Get a list of notifications for the user

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

Change bulb colour

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 colour of the bulb

Change bulb effect

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 effects of the bulb

Set night vision to auto mode

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 ser night vision to auto mode

Turn off all effects

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 all effects of the bulb

Turn off all home devices

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 all the Smitch Home devices (bulbs, plugs and power strips)

Turn off camera

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 camera

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 device

Turn off human detection

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 human detection

Turn off mic

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 mic

Turn off motion detection

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 motion detection

Turn off night vision

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 night vision

Turn off object tracking

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 object tracking

A motion 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 when a motion detected

A sound 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 when a sound is detected

Change bulb colour

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 colour of the bulb

Change bulb effect

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 effects of the bulb

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

Get list of notifications

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.
Get a list of notifications for the user

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

Build an automation in seconds!

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

GET STARTED

How to connect to a Smitch automation

Find an automation using Smitch

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

Connect IFTTT to your Smitch 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 Smitch and Zubie

About Smitch

SMART HOME STARTS HERE

Manage your Smart Home from anywhere easily

Connect your Smitch devices with hundreds of other services. Stay smart and secure with Smitch

Connect Smitch

More integrations with Smitch

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