Close menu
Explore Plans
Mobile menu Close menu
Back

Huma-i to MCONNECT integrations

Automate your workflows between Huma-i and MCONNECT with IFTTT.

Create your own Huma-i and MCONNECT 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.

16 triggers, queries, and actions

VOCs Alert

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 if VOC (Volatile Organic Compounds) level measured from your Huma-i device rises above the specified threshold, which is the average for 5 minutes.

AQI Levels Detect Alert

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 if the AQI measured from your Huma-i device rises above the specified threshold, which is the average for 5 minutes.

Carbon Dioxide(CO₂) Alert

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 if the concentration of Carbon Dioxide (CO₂) measured from your Huma-i device rises above the specified threshold, which is the average for 5 minutes.

High Humidity Alert

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 humidity measured from your Huma-i device rises above the threshold you specified.

High Temperature Alert

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 measured from your Huma-i device rises above the threshold you specified.

Huma-i Device Data Trigger

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 Huma-i device data update.

Low Humidity Alert

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 humidity measured from your Huma-i device dropped below the specified threshold, which is the average for 5 minutes.

Low Temperature Alert

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 measured from your Huma-i drops below the threshold you specified.

Opened/Closed

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 an MCONNECT device opened or closed.

PM2.5 Alert

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 if the level of PM2.5 concentration measured from your Huma-i device rises above the specified threshold, which is the average for 5 minutes.

Turned ON/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 an MCONNECT device is turned ON or OFF.

History of device

Pro plus icon
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 the device history

Activate RF transmitter

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 activate the RF channel of your MCONNECT device.

Activate scene

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 activate one MCONNECT scene.

Open/Close

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/close your MCONNECT device.

Turn ON/OFF

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/OFF your MCONNECT device.

VOCs Alert

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 if VOC (Volatile Organic Compounds) level measured from your Huma-i device rises above the specified threshold, which is the average for 5 minutes.

Activate RF transmitter

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 activate the RF channel of your MCONNECT device.

Activate scene

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 activate one MCONNECT scene.

AQI Levels Detect Alert

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 if the AQI measured from your Huma-i device rises above the specified threshold, which is the average for 5 minutes.

Carbon Dioxide(CO₂) Alert

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 if the concentration of Carbon Dioxide (CO₂) measured from your Huma-i device rises above the specified threshold, which is the average for 5 minutes.

High Humidity Alert

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 humidity measured from your Huma-i device rises above the threshold you specified.

High Temperature Alert

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 measured from your Huma-i device rises above the threshold you specified.

History of device

Pro plus icon
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 the device history

Huma-i Device Data Trigger

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 Huma-i device data update.

Low Humidity Alert

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 humidity measured from your Huma-i device dropped below the specified threshold, which is the average for 5 minutes.

Low Temperature Alert

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 measured from your Huma-i drops below the threshold you specified.

Open/Close

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/close your MCONNECT device.

Build an automation in seconds!

You can add delays, queries, and more actions in the next step!

GET STARTED

How to connect to a Huma-i automation

Find an automation using Huma-i

Find an automation to connect to, or create your own!

Connect IFTTT to your Huma-i 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!
Get started

Upgrade your automations with

Start your free trial

More on Huma-i and MCONNECT

About Huma-i

This service is for Humatech's air quality monitor.

Connect Huma-i

More integrations with Huma-i

About MCONNECT

Control your MCONNECT devices from IFTTT.

Create applets to turn on lights, open the gate and more.

Connect MCONNECT

More integrations with MCONNECT