Send myself an e-mail with my swimming pool water measurements
Popular Blue Connect workflows & automations
-
13
-
-
Log measurements of your swimming pool water in a Google spreadsheet
32
-
-
Send an email when the pH has turned too high
15
-
-
Turn on/off my eWeLink switch when the temperature >= setpoint
-
-
Turn on/off my eWeLink switch when the temperature is < setpoint
-
-
If ORP of pool Pool becomes too low, then turn on plug Pump
-
-
Send a notification when water temp in the pool has turned too low
-
Create your own 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.
28 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.
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 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.
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 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.
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 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.
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.
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.
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.
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".
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".
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".
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 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 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 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.
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 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 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"
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.
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 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.
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 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.
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 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.
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.
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.
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.
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".
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".
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".
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 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 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 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.
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 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 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"
