HumidityHigh action
Other popular Alexa Actions by mkZense workflows and automations
-
1
-
-
Motion is detected on Wyze Cam , then send IFTTTrigger-2 action to your Alexa device
1
-
-
HumidityNormal action
1
-
-
Real-time Weather Status Starts Alexa Routine
4
-
-
Fasting time routine on Alexa from mkZense
4
-
-
send IFTTTrigger-2 action to your Alexa device
1.21K
-
-
Smart Routine Trigger
-
-
Prayer time routine on Alexa from mkZense
277
-
-
Miele Wärmelade An
-
Create your own Alexa Actions by mkZense and Blue Connect 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.
29 triggers, queries, and actions
New water measurement
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 new water measurement of a swimming pool is available.
No measurement received
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 no measurement has been received for the last 2 hours.
ORP becomes OK
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 ORP of your pool water has been evaluated as OK according to your swimming pool target values.
ORP becomes too high
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 ORP of your pool water has been evaluated as too high according to your swimming pool target values.
ORP becomes too low
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 ORP of your pool water has been evaluated as too low according to your swimming pool target values.
ORP is < setpoint
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 ORP of your pool water is smaller than your swimming pool "ORP setpoint".
ORP is >= setpoint
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 ORP of your pool water is greather or equal to your swimming pool "ORP setpoint".
PH becomes OK
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 pH of your pool water has been evaluated as OK according to your swimming pool target values.
PH becomes too high
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 pH of your pool water has been evaluated as too high according to your swimming pool target values.
PH becomes too low
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 pH of your pool water has been evaluated as too low according to your swimming pool target values.
PH is <= setpoint
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 pH of your pool water is lower or equal to your swimming pool "pH setpoint".
PH is > setpoint
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 pH of your pool water is greater than your swimming pool "pH setpoint".
Salinity becomes OK
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 salinity of your pool water has been evaluated as OK according to your swimming pool target values.
Salinity becomes too high
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 salinity of your pool water has been evaluated as too high according to your swimming pool target values.
Salinity becomes too low
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 salinity of your pool water has been evaluated as too low according to your swimming pool target values.
Temperature becomes OK
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 temperature of your pool water has been evaluated as OK according to your swimming pool target values.
Temperature becomes too high
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 temperature of your pool water has been evaluated as too high according to your swimming pool target values.
Temperature becomes too low
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 temperature of your pool water has been evaluated as too low according to your swimming pool target values.
Temperature is < setpoint
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 temperature of your pool water is lower than your swimming pool "temperature setpoint".
Temperature is >= setpoint
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 temperature of your pool water is greater or equal to your swimming pool "temperature setpoint".
History of ORP becomes too high
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 ORP of your pool water was been evaluated as too high according to your swimming pool target values.
History of ORP OK evaluations
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 times the ORP of your pool water was evaluated as OK according to your swimming pool target values.
History of pH becomes OK
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 pH of your pool water was been evaluated as OK according to your swimming pool target values.
History of recent "ORP is < setpoint" alerts
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 alerts when the ORP of your swimming pool water was smaller than your swimming pool "ORP setpoint"
History of salinity becomes too high
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 salinity of your pool water was been evaluated as too high according to your swimming pool target values.
History of salinity becomes too low
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 salinity of your pool water was been evaluated as too low according to your swimming pool target values.
History of water measurement
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 every time a new water measurement of a swimming pool was available.
History of when temperature became too high
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 of your pool water was been evaluated as too high according to your swimming pool target values.
sendAlexaActionByMkzense
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 service from mkZense will send an action to run a routine on your Alexa device. Use it to add Voice to your Applet.
History of ORP becomes too high
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 ORP of your pool water was been evaluated as too high according to your swimming pool target values.
History of ORP OK evaluations
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 times the ORP of your pool water was evaluated as OK according to your swimming pool target values.
History of pH becomes OK
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 pH of your pool water was been evaluated as OK according to your swimming pool target values.
History of recent "ORP is < setpoint" alerts
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 alerts when the ORP of your swimming pool water was smaller than your swimming pool "ORP setpoint"
History of salinity becomes too high
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 salinity of your pool water was been evaluated as too high according to your swimming pool target values.
History of salinity becomes too low
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 salinity of your pool water was been evaluated as too low according to your swimming pool target values.
History of water measurement
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 every time a new water measurement of a swimming pool was available.
History of when temperature became too high
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 of your pool water was been evaluated as too high according to your swimming pool target values.
New water measurement
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 new water measurement of a swimming pool is available.
No measurement received
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 no measurement has been received for the last 2 hours.
ORP becomes OK
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 ORP of your pool water has been evaluated as OK according to your swimming pool target values.
ORP becomes too high
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 ORP of your pool water has been evaluated as too high according to your swimming pool target values.
ORP becomes too low
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 ORP of your pool water has been evaluated as too low according to your swimming pool target values.
ORP is < setpoint
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 ORP of your pool water is smaller than your swimming pool "ORP setpoint".
ORP is >= setpoint
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 ORP of your pool water is greather or equal to your swimming pool "ORP setpoint".
PH becomes OK
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 pH of your pool water has been evaluated as OK according to your swimming pool target values.
PH becomes too high
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 pH of your pool water has been evaluated as too high according to your swimming pool target values.
PH becomes too low
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 pH of your pool water has been evaluated as too low according to your swimming pool target values.
PH is <= setpoint
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 pH of your pool water is lower or equal to your swimming pool "pH setpoint".
PH is > setpoint
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 pH of your pool water is greater than your swimming pool "pH setpoint".
Salinity becomes OK
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 salinity of your pool water has been evaluated as OK according to your swimming pool target values.
Salinity becomes too high
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 salinity of your pool water has been evaluated as too high according to your swimming pool target values.
Salinity becomes too low
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 salinity of your pool water has been evaluated as too low according to your swimming pool target values.
sendAlexaActionByMkzense
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 service from mkZense will send an action to run a routine on your Alexa device. Use it to add Voice to your Applet.
Temperature becomes OK
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 temperature of your pool water has been evaluated as OK according to your swimming pool target values.
Temperature becomes too high
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 temperature of your pool water has been evaluated as too high according to your swimming pool target values.
Temperature becomes too low
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 temperature of your pool water has been evaluated as too low according to your swimming pool target values.
Temperature is < setpoint
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 temperature of your pool water is lower than your swimming pool "temperature setpoint".
Temperature is >= setpoint
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 temperature of your pool water is greater or equal to your swimming pool "temperature setpoint".
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 Alexa Actions by mkZense automation
Find an automation using Alexa Actions by mkZense
Find an automation to connect to, or create your own!Connect IFTTT to your Alexa Actions by mkZense 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
Top integration tips, tools, and resources
More on Discord and Instagram
About Alexa Actions by mkZense
Send Actions to your Alexa device from IFTTT. Your Alexa speaker can respond to this action using Alexa routines.
Send Actions to your Alexa device from IFTTT. Your Alexa speaker can respond to this action using Alexa routines.
About Blue Connect
Unlock the full potential of your Blue Connect. Trigger actions of your choice every time something happens in your swimming pool.
Unlock the full potential of your Blue Connect. Trigger actions of your choice every time something happens in your swimming pool.