If Earzz recognises the sound I want, then change the colour of my Philips Hue light(s) to Red
Other popular EARZZ workflows and automations
-
-
If Earzz recognises the sound I want, then change the colour of my Philips Hue light(s) to Green
-
If Earzz recognises the sound I want, then send yourself an email
-
If Earzz recognises the sound I want, then activate my remote pet feeder
-
If Earzz recognises the sound I want, then set heat mode on my Heatzy device
-
Send a web request (Webhook) when a sound is recognized by Earzz
-
If Earzz recognises the sound I want, then pause Spotify playback
-
If Earzz recognises the sound I want, then set the temperature on my Heatmiser device
-
If Earzz recognises the sound I want, then set Heat mode on my Smart life Heater
Create your own EARZZ and Sensatio 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
If a sound is recognised by Earzz
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 sound is recognised by Earzz
Sensor Data below Limit
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 event is fired when there is new sensor data that falls below a defined lower limit
Sensor Data exceeds Limit
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 event is fired when there is new sensor data that exceeds a defined upper limit
Sensor Timeout
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 event is fired when there is no new sensor data for a specified amount of time.
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 event was fired when there was new sensor data that fell below a defined lower limit Note: this query will only return future events after this Applet is created.
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 event was fired when there was new sensor data that fell below a defined lower limit Note: this query will only return future events after this Applet is created.
If a sound is recognised by Earzz
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 sound is recognised by Earzz
Sensor Data below Limit
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 event is fired when there is new sensor data that falls below a defined lower limit
Sensor Data exceeds Limit
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 event is fired when there is new sensor data that exceeds a defined upper limit
Sensor Timeout
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 event is fired when there is no new sensor data for a specified amount of time.
GET STARTED
How to connect to a EARZZ automation
Find an automation using EARZZ
Find an automation to connect to, or create your own!Connect IFTTT to your EARZZ 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
More on EARZZ and Sensatio
About EARZZ
From a knock at the door to a smoke alarm, Earzz alerts on your watches, phones and tablets for important sounds at home, no matter where you are!
From a knock at the door to a smoke alarm, Earzz alerts on your watches, phones and tablets for important sounds at home, no matter where you are!
About Sensatio
Triggers and Actions exposed by the Sensate Cloud. Use one of the Sensate Apps to generate a sensor API key to expose its data to IFTTT.
Triggers and Actions exposed by the Sensate Cloud. Use one of the Sensate Apps to generate a sensor API key to expose its data to IFTTT.