Slack to Zubie integrations Automate your workflows between Discord and Instagram with IFTTT.

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

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

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.

Vehicle leaves 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 leaves a place.

Vehicle out of range

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 Triggers when your vehicle is further than an allowed distance from a specific 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 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.

History of when Check engine light was on for any vehicle

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

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.

Post to channel

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 post a message to the channel you choose in Slack.

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

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

History of when Check engine light was on for any vehicle

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

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.

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.

Post to channel

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 post a message to the channel you choose in Slack.

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.

Vehicle leaves 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 leaves a place.

Vehicle out of range

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 Triggers when your vehicle is further than an allowed distance from a specific location.
GET STARTED

How to connect to a Slack automation

Find an automation using Slack

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

Connect IFTTT to your Slack 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 Discord and Instagram

About Slack

Slack brings all your team communication into one place. Turn on Applets to bring important information into channels, quickly share photos, automate reminders, and much more.

Connect Slack

More integrations with Slack

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