Close a Hubitat shut-off valve when a Wireless Tag detects water
Other popular Hubitat workflows and automations
-
-
-
When Roomba Starts a Job Turn On a Hubitat Device
2
-
-
Email me when the temperature of a Hubitat device drops below threshold
38
-
-
Set Fanimation device when your Habitat device turn off
-
-
Tap to dim a Hubitat device
28
-
-
Lock a Hubitat device when Flic is clicked
-
-
Turn on a Hubitat device when Ring detects motion
154
-
-
If Number 96 turns on, then Switch on Number 97
1
-
-
Turn on a Hubitat device when Flic is clicked
10
-
Create your own Hubitat and Kennedy-Mighell Report Podcast 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.
27 triggers, queries, and actions
Device closes
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 your Hubitat device closes.
Device opens
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 your Hubitat device opens.
Device turns off
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 your Hubitat device turns off.
Device turns on
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 your Hubitat device turns on.
Mode changes
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 the Hubitat mode changes.
Motion is 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 new motion is detected.
Motion is no longer 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 motion is no longer detected.
New Episode
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 there is a new episode available for the Kennedy-Mighell Report Podcast
Presence is 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 every time your Hubitat device's presence is detected.
Presence is no longer 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 every time your Hubitat device's presence is no longer detected.
Temperature drops below
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 the temperature drops below the specified threshold.
Temperature rises above
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 the temperature rises above the specified threshold.
History of Device 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 your Hubitat device turned off.
History of Mode changes
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 the Hubitat mode has changed.
History of temperature rises above
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 the temperature rises above the specified threshold. Note: this query will only return future events after this Applet is created.
Recent history of device opens
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 recent times when your Habitat device opened.
Recent history of Device turns on
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 recent Hubitat device turns on events.
Change 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 change Hubitat's mode.
Close a 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 close a Hubitat device.
Dim a 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 change a device's dimmer level.
Lock a 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 lock a Hubitat device.
Open a 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 open a Hubitat device.
Turn off a 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 Hubitat switches, lights, sirens, strobes, etc.
Turn on a 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 a device attached to your Hubitat Elevation system.
Unlock a 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 unlock a Hubitat device.
Change 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 change Hubitat's mode.
Close a 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 close a Hubitat device.
Device closes
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 your Hubitat device closes.
Device opens
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 your Hubitat device opens.
Device turns off
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 your Hubitat device turns off.
Device turns on
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 your Hubitat device turns on.
Dim a 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 change a device's dimmer level.
History of Device 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 your Hubitat device turned off.
History of Mode changes
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 the Hubitat mode has changed.
History of temperature rises above
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 the temperature rises above the specified threshold. Note: this query will only return future events after this Applet is created.
Lock a 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 lock a Hubitat device.
Mode changes
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 the Hubitat mode changes.
Build an automation in seconds!
If
Select a trigger the automation will use
Then
Select an action the automation will perform
You can add delays, queries, and more actions in the next step!
GET STARTED
How to connect to a Hubitat automation
Find an automation using Hubitat
Find an automation to connect to, or create your own!Connect IFTTT to your Hubitat 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!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 Hubitat and Kennedy-Mighell Report Podcast
About Hubitat
Hubitat Elevation is a powerful home automation platform that works with your connected devices. Hubitat is a local solution, not cloud-dependent, so it’s fast, reliable and private.
Hubitat Elevation is a powerful home automation platform that works with your connected devices. Hubitat is a local solution, not cloud-dependent, so it’s fast, reliable and private.
About Kennedy-Mighell Report Podcast
The Kennedy-Mighell Report is a popular legal technology podcast that provides insightful perspectives on the intersection of law, technology, and legal practice. Hosted by Dennis Kennedy and Tom Mighell, two seasoned legal professionals and tech enthusiasts, the podcast offers practical advice and timely tips to help legal practitioners navigate the tech world. The hosts discuss a wide range of topics, from the latest tech trends impacting the legal sphere to techniques for improving law firm efficiency using technology.
The Kennedy-Mighell Report is a popular legal technology podcast that provides insightful perspectives on the intersection of law, technology, and legal practice. Hosted by Dennis Kennedy and Tom Mighell, two seasoned legal professionals and tech enthusiasts, the podcast offers practical advice and timely tips to help legal practitioners navigate the tech world. The hosts discuss a wide range of topics, from the latest tech trends impacting the legal sphere to techniques for improving law firm efficiency using technology.