Send Telegram message when a Hubitat device turns on
10 ready-made Hubitat and Telegram Applets
Turn one on, or build your own. Hubitat can start an automation with "Device closes", and IFTTT can then run "Send message" on Telegram.-
-
-
Send Telegram message when Hubitat mode changes
-
-
Send Telegram message when Hubitat water sensor is dry
-
-
Send Telegram message when Hubitat temperature drops below threshold
-
-
Send Telegram message when a Hubitat device turns off
-
-
Send Telegram message when water is detected by Hubitat
-
-
Close Hubitat device and send Telegram message when a MyQ door closes
-
-
Turn on a Hubitat device when a Telegram command is sent in a group
-
-
Turn off Hubitat lights when you send a key phrase to Telegram
-
Automate Hubitat and Telegram from your AI assistant
Ask Copilot to create Hubitat applets and control your smart home devices with IFTTT MCP.
Set up IFTTT MCP
Create your own Hubitat and Telegram 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.
42 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 message in a group
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 user sends the /ifttt command to the source group.
New message with key phrase in a group
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 user sends a message with the /ifttt command and a key phrase to the source group.
New message with key phrase to @IFTTT
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 you send a text message with a key phrase to the @IFTTT bot on Telegram.
New photo in your channel
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 new photo is posted in a public channel where you are an admin. The @IFTTT bot must also be an admin in the channel.
New photo to @IFTTT on Telegram
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 you send a photo to the @IFTTT bot on Telegram.
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 messages in a group
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 user sends the /ifttt command to the source group.
History of messages with key phrase in a group
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 user sends a message with the /ifttt command and a key phrase to the source group.
History of messages with key phrase to @IFTTT
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 you send a text message with a key phrase to the @IFTTT bot on Telegram.
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 photos in your channel
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 new photo is posted in a public channel where you are an admin. The @IFTTT bot must also be an admin in the channel.
History of photos to @IFTTT on Telegram
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 you send a photo to the @IFTTT bot on Telegram.
History of posts in your channel
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 new message is posted in a public channel where you are an admin. The @IFTTT bot must also be an admin in the channel.
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.
Send message
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 a text message to a Telegram chat.
Send mp3
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 an mp3 to a Telegram chat.
Send photo
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 a photo to a Telegram chat.
Send video
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 a video to a Telegram chat.
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 messages in a group
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 user sends the /ifttt command to the source group.
History of messages with key phrase in a group
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 user sends a message with the /ifttt command and a key phrase to the source group.
History of messages with key phrase to @IFTTT
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 you send a text message with a key phrase to the @IFTTT bot on Telegram.
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.
Build an automation in seconds!
If
Select a trigger the automation will use
Device closes
Device opens
Device turns off
Device turns on
Mode changes
Motion is detected
Motion is no longer detected
New message in a group
New message with key phrase in a group
New message with key phrase to @IFTTT
New photo in your channel
New photo to @IFTTT on Telegram
New post in your channel
Presence is detected
Presence is no longer detected
Temperature drops below
Temperature rises above
Water is detected
Water is no longer detected
Then
Select an action the automation will perform
Change Mode
Close a device
Dim a device
Lock a device
Open a device
Send message
Send mp3
Send photo
Send video
Turn off a device
Turn on a device
Unlock a device
You can add delays, queries, and more actions in the next step!
GET STARTED
How to connect to a Hubitat automation
Find an Applet using Hubitat and Telegram
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
Hubitat and Telegram tips, tools, and resources
More on Hubitat and Telegram
About Hubitat
Hubitat and IFTTT let you automate your connected devices based on motion, temperature, water detection, and more.
About Telegram
Telegram and IFTTT let you automatically send messages and media to chats and channels, so you can keep your community in the loop without doing it manually.