When PM2.5 levels become unhealthy, set Lennox iComfort fan to On
Popular HAVEN IAQ workflows & automations
-
-
-
When PM2.5 levels become unhealthy, set Honeywell Total Connect fan to On
-
-
Set my thermostat fan to continuous for 30 min when HAVEN detects unhealthy tVOC levels
-
-
Set my thermostat fan to continuous for 30 min when HAVEN detects unhealthy PM2.5 levels
-
-
Run My Thermostat Schedule When Haven IAQ VOC Level is Back to a Healthy Reading
-
-
Set My Thermostat Fan to Run Once When Haven IAQ VOC Level Reaches an Unhealthy Reading
-
-
Run My Thermostat Schedule When Haven IAQ PM Level is Back to a Healthy Reading
-
-
When PM2.5 levels become unhealthy, toggle a Kasa Switch or Plug & create a Google Calendar event
-
Create your own HAVEN IAQ 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.
5 triggers, queries, and actions
PM2.5 threshold is crossed
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 whenever the measured Particulate Matter of 2.5 microns in size (PM2.5) is above or below the threshold.
Relative Humidity threshold is crossed
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 whenever the measured Relative Humidity (RH) is above or below the threshold.
Temperature threshold is crossed
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 whenever the measured temperature is above or below the threshold.
VOC threshold is crossed
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 whenever the measured Volatile Organic Compounds (VOCs) is above or below the threshold.
List all events
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 all the different event types.
PM2.5 threshold is crossed
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 whenever the measured Particulate Matter of 2.5 microns in size (PM2.5) is above or below the threshold.
Relative Humidity threshold is crossed
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 whenever the measured Relative Humidity (RH) is above or below the threshold.
Temperature threshold is crossed
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 whenever the measured temperature is above or below the threshold.
VOC threshold is crossed
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 whenever the measured Volatile Organic Compounds (VOCs) is above or below the threshold.
List all events
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 all the different event types.
