Trigger littleBit Servo for 3 seconds
Other popular littleBits workflows and automations
-
8
-
-
If I'm low on Toilet Paper, add buying it to my errands list.
4
-
-
cfl youtube like
2
-
-
If new hour, then trigger cloud module
92
-
-
Create a School Bell System with Google Calendar and Littlebits.
3
-
-
Pumpkin hashtag
5
-
-
Set output level 0-100
32
-
-
If somebody mentions you on twitter, trigger the servo!
4
-
-
Trigger MESH if littleBits cloudBit is turned on
5
-
USE CASE
Automated notifications for smart devices
Integrate littleBits with Notifications to receive instant alerts when your devices are triggered, such as when your littleBits doorbell rings.
Get startedCreate your own littleBits and Wireless Tag 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.
60 triggers, queries, and actions
Back in range
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 specified tag comes out of "out of range" state. Only tags with auto-update is enabled can come out of "out of range" state.
Brightness returns to normal
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 specified tag senses that its ambient light intensity returns between the upper and lower thresholds configured at light options screen inside the WirelessTag app.
Door or window is 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 a specified motion sensor tag(s) or reed sensor(s) detect that a door or window is closed.
Door or window is opened
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 specified motion sensor tag(s) or reed sensor(s) detect that a door or window is open.
Humidity or moisture is 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 a specified tag with humidity or moisture monitoring enabled, detects "too wet" state. Adjust the threshold from the humidity/moisture options screen inside the WirelessTag app.
Humidity or moisture is 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 a specified tag with humidity or moisture monitoring enabled, detects "too dry" state. Adjust the threshold from the humidity/moisture options screen inside the WirelessTag app.
Humidity or moisture returns to normal
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 specified tag with humidity or moisture monitoring enabled, returns within normal humidity range. Adjust the upper/lower thresholds from the humidity/moisture options screen inside the WirelessTag app.
Motion sensor has timed out
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 specified PIR KumoSensor or regular motion sensor tag detects no movement for a time-out period.
Movement is detected
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 specified PIR KumoSensor detects movement.
New KumoApp message
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 specific KumoApp produces a log message with KumoApp.Log call with a specific type.
Out of range
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 specified tag goes out of range. Note that the system can only determine whether a tag is out of range, if the "auto-update" is enabled.
Sensor detects water
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 specified water sensor tag detects water with its resistive sensor, or when you short circuit its tip.
Sensor no longer detects water
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 specified water sensor tag transitions from detected water state to not detected water state, or when you open circuit its tip.
Tag is moved
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 specified motion sensor tag(s) armed in motion detection mode, have moved.
Tag Manager Offline
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 server detects that specified tag manager lost Internet connection due to power outage or Internet connection problems.
Tag Manager Online
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 specified tag manager is back online.
Temperature is 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 a specified tag senses that its ambient temperature exceeds an upper threshold configured at temperature options screen inside the WirelessTag app.
Temperature is 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 a specified tag senses that its ambient temperature falls below an lower threshold configured at temperature options screen inside the WirelessTag app.
Temperature returns to normal
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 specified tag senses that its ambient temperature returns between the upper and lower thresholds configured at temperature options screen inside the WirelessTag app.
Too bright
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 specified tag senses that its ambient light exceeds an upper threshold configured at light options screen inside the WirelessTag app. For example, this can be used to detect fridge door open.
Too dark
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 specified tag senses that its ambient light exceeds an lower threshold configured at light options screen inside the WirelessTag app. For example, this can be used to turn on a light in a room.
Turned 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 every time your cloudBit's input goes from high to low.
Turned On
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 your cloudBit receives an input signal from another littleBits module.
Update 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 every time a temperature/humidity/lux update is received from specified sensor/tag(s).
Current Tag Manager State
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.
The query returns if the specified tag manager is online or offline, as well as how many hours it has been online.
Current Tag State
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 specified door/window sensor/tag's current state, including temperature, humidity/lux (when available) and motion state such as door open/close, moved, or detected motion (for PIR sensor)
History of door or window is closed
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 a specified motion sensor tag(s) or reed sensor(s) detect that a door or window was closed.
History of door or window is opened
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 a specified motion sensor tag(s) or reed sensor(s) detect that a door or window was open.
History of High Temperature 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 times when a specified tag senses that its ambient temperature exceeded an upper threshold configured at temperature options screen inside the WirelessTag app. Note: this query will only return future events after this Applet
History of humidity or moisture is 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 a specified tag with humidity or moisture monitoring enabled, detects "too wet" state.
History of KumoApp messages
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 specific KumoApp produces a log message with KumoApp.Log call with a specific type.
History of motion sensor has timed out
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 specified PIR KumoSensor or regular motion sensor tag detects no movement for a time-out period.
History of sensor no longer detects water
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 specified water sensor tag transitions from detected water state to not detected water state, or when you open circuit its tip.
History of tag manager offline
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 server detects that specified tag manager lost Internet connection due to power outage or Internet connection problems.
History of tag moves
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 specified motion sensor tag(s) armed in motion detection mode, have moved.
History of tag out of range
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 a specified tag goes out of range. Note that the system can only determine whether a tag was out of range, if the "auto-update" was enabled.
History of temperature returning to normal
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 specified tag sensed that its ambient temperature had returned between the upper and lower thresholds configured on the temperature options screen inside the WirelessTag app. Note: this query will only return future e
History of too bright
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 a specified tag senses that its ambient light exceeds an upper threshold configured at light options screen inside the WirelessTag app. Note: this query will only return future events after this Applet is created.
History of update received
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 a temperature/humidity/lux update was received from specified sensor/tag(s).
History of when input dropped
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 your cloudBit's input goes from high to low. Note: this query will only return future events after this Applet is created.
History of when temperature was 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 a specified tag sensed that its ambient temperature fell below a threshold. Note: this query will only return future events after this Applet is created.
History of when the tag manager was online
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 specified tag manager was back online.
Activate Output
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 output of your cloudBit for 3 seconds.
Arm motion sensor
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 arms motion sensor on a tag. Regular angle based motion sensor, Reed KumoSensor and PIR KumoSensor can all be armed using this action.
Beep a tag
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 beep the tag. NOTE: Only compatible with the Motion Sensor Tags with buzzer.
Deactivate Output
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 deactivate the output of your cloudBit.
Disable brightness monitoring
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 disable brightness/ambient light intensity monitoring on a tag.
Disable humidity or moisture monitoring
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 disable humidity or moisture monitoring on a tag.
Disable temperature monitoring
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 disable temperature monitoring on a tag.
Disarm motion sensor
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 disarms motion sensor on a tag. Regular angle based motion sensor, Reed KumoSensor and PIR KumoSensor can all be disarmed using this action.
Enable brightness monitoring
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 enable brightness/ambient light intensity monitoring on a tag. NOTE: Only compatible with Tags with ambient light sensor.
Enable humidity or moisture monitoring
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 enable humidity or moisture monitoring on a tag. NOTE: Only compatible with Tags with humidity or moisture sensor.
Enable temperature monitoring
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 enable temperature monitoring on a tag.
Run a KumoApp
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 start a KumoApp installed under the current user account. If the KumoApp is running, nothing will happen. If a KumoApp does not register any event handler or timer, it will automatically stop after executing the first time, allowing this action to run multiple times without user intervention.
Set Output Level
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 set the output of your cloudBit to the specified level for the specified length of time.
Stop a KumoApp
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 stop a KumoApp. If the KumoApp is not running, nothing will happen.
Stop beeping a tag
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 stop the tag beeping. This action can also be used to test tag connectivity.
Turn off light or switch
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 off LED on the tag or a WeMo device.
Turn on light or switch
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 LED on the tag or a WeMo device.
Update Temperature/Humidity/Lux
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 force an update to read the current temperature, humidity and ambient light (when available).
Activate Output
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 output of your cloudBit for 3 seconds.
Arm motion sensor
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 arms motion sensor on a tag. Regular angle based motion sensor, Reed KumoSensor and PIR KumoSensor can all be armed using this action.
Back in range
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 specified tag comes out of "out of range" state. Only tags with auto-update is enabled can come out of "out of range" state.
Beep a tag
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 beep the tag. NOTE: Only compatible with the Motion Sensor Tags with buzzer.
Brightness returns to normal
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 specified tag senses that its ambient light intensity returns between the upper and lower thresholds configured at light options screen inside the WirelessTag app.
Current Tag Manager State
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.
The query returns if the specified tag manager is online or offline, as well as how many hours it has been online.
Current Tag State
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 specified door/window sensor/tag's current state, including temperature, humidity/lux (when available) and motion state such as door open/close, moved, or detected motion (for PIR sensor)
Deactivate Output
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 deactivate the output of your cloudBit.
Disable brightness monitoring
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 disable brightness/ambient light intensity monitoring on a tag.
Disable humidity or moisture monitoring
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 disable humidity or moisture monitoring on a tag.
Disable temperature monitoring
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 disable temperature monitoring on a tag.
Disarm motion sensor
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 disarms motion sensor on a tag. Regular angle based motion sensor, Reed KumoSensor and PIR KumoSensor can all be disarmed using this action.
Door or window is 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 a specified motion sensor tag(s) or reed sensor(s) detect that a door or window is closed.
Door or window is opened
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 specified motion sensor tag(s) or reed sensor(s) detect that a door or window is open.
Enable brightness monitoring
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 enable brightness/ambient light intensity monitoring on a tag. NOTE: Only compatible with Tags with ambient light sensor.
Enable humidity or moisture monitoring
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 enable humidity or moisture monitoring on a tag. NOTE: Only compatible with Tags with humidity or moisture sensor.
Enable temperature monitoring
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 enable temperature monitoring on a tag.
History of door or window is closed
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 a specified motion sensor tag(s) or reed sensor(s) detect that a door or window was closed.
History of door or window is opened
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 a specified motion sensor tag(s) or reed sensor(s) detect that a door or window was open.
History of High Temperature 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 times when a specified tag senses that its ambient temperature exceeded an upper threshold configured at temperature options screen inside the WirelessTag app. Note: this query will only return future events after this Applet
History of humidity or moisture is 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 a specified tag with humidity or moisture monitoring enabled, detects "too wet" state.
History of KumoApp messages
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 specific KumoApp produces a log message with KumoApp.Log call with a specific type.
History of motion sensor has timed out
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 specified PIR KumoSensor or regular motion sensor tag detects no movement for a time-out period.
History of sensor no longer detects water
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 specified water sensor tag transitions from detected water state to not detected water state, or when you open circuit its tip.
History of tag manager offline
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 server detects that specified tag manager lost Internet connection due to power outage or Internet connection problems.
History of tag moves
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 specified motion sensor tag(s) armed in motion detection mode, have moved.
History of tag out of range
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 a specified tag goes out of range. Note that the system can only determine whether a tag was out of range, if the "auto-update" was enabled.
History of temperature returning to normal
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 specified tag sensed that its ambient temperature had returned between the upper and lower thresholds configured on the temperature options screen inside the WirelessTag app. Note: this query will only return future e
History of too bright
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 a specified tag senses that its ambient light exceeds an upper threshold configured at light options screen inside the WirelessTag app. Note: this query will only return future events after this Applet is created.
History of update received
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 a temperature/humidity/lux update was received from specified sensor/tag(s).
History of when input dropped
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 your cloudBit's input goes from high to low. Note: this query will only return future events after this Applet is created.
History of when temperature was 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 a specified tag sensed that its ambient temperature fell below a threshold. Note: this query will only return future events after this Applet is created.
History of when the tag manager was online
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 specified tag manager was back online.
Humidity or moisture is 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 a specified tag with humidity or moisture monitoring enabled, detects "too wet" state. Adjust the threshold from the humidity/moisture options screen inside the WirelessTag app.
Humidity or moisture is 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 a specified tag with humidity or moisture monitoring enabled, detects "too dry" state. Adjust the threshold from the humidity/moisture options screen inside the WirelessTag app.
Humidity or moisture returns to normal
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 specified tag with humidity or moisture monitoring enabled, returns within normal humidity range. Adjust the upper/lower thresholds from the humidity/moisture options screen inside the WirelessTag app.
Motion sensor has timed out
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 specified PIR KumoSensor or regular motion sensor tag detects no movement for a time-out period.
Movement is detected
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 specified PIR KumoSensor detects movement.
New KumoApp message
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 specific KumoApp produces a log message with KumoApp.Log call with a specific type.
Out of range
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 specified tag goes out of range. Note that the system can only determine whether a tag is out of range, if the "auto-update" is enabled.
Run a KumoApp
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 start a KumoApp installed under the current user account. If the KumoApp is running, nothing will happen. If a KumoApp does not register any event handler or timer, it will automatically stop after executing the first time, allowing this action to run multiple times without user intervention.
Sensor detects water
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 specified water sensor tag detects water with its resistive sensor, or when you short circuit its tip.
Sensor no longer detects water
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 specified water sensor tag transitions from detected water state to not detected water state, or when you open circuit its tip.
Set Output Level
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 set the output of your cloudBit to the specified level for the specified length of time.
Stop a KumoApp
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 stop a KumoApp. If the KumoApp is not running, nothing will happen.
Stop beeping a tag
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 stop the tag beeping. This action can also be used to test tag connectivity.
Tag is moved
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 specified motion sensor tag(s) armed in motion detection mode, have moved.
Tag Manager Offline
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 server detects that specified tag manager lost Internet connection due to power outage or Internet connection problems.
Tag Manager Online
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 specified tag manager is back online.
Temperature is 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 a specified tag senses that its ambient temperature exceeds an upper threshold configured at temperature options screen inside the WirelessTag app.
Temperature is 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 a specified tag senses that its ambient temperature falls below an lower threshold configured at temperature options screen inside the WirelessTag app.
Temperature returns to normal
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 specified tag senses that its ambient temperature returns between the upper and lower thresholds configured at temperature options screen inside the WirelessTag app.
Too bright
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 specified tag senses that its ambient light exceeds an upper threshold configured at light options screen inside the WirelessTag app. For example, this can be used to detect fridge door open.
Too dark
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 specified tag senses that its ambient light exceeds an lower threshold configured at light options screen inside the WirelessTag app. For example, this can be used to turn on a light in a room.
Turn off light or switch
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 off LED on the tag or a WeMo device.
Turn on light or switch
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 LED on the tag or a WeMo device.
Turned 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 every time your cloudBit's input goes from high to low.
Turned On
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 your cloudBit receives an input signal from another littleBits module.
Update 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 every time a temperature/humidity/lux update is received from specified sensor/tag(s).
Update Temperature/Humidity/Lux
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 force an update to read the current temperature, humidity and ambient light (when available).
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 littleBits automation
Find an automation using littleBits
Find an automation to connect to, or create your own!Connect IFTTT to your littleBits 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 Discord and Instagram
About littleBits
littleBits is an opensource library of electronic modules that snap together with magnets for prototyping, learning and fun. Connect your littleBits Cloud module to every thing on the internet!
littleBits is an opensource library of electronic modules that snap together with magnets for prototyping, learning and fun. Connect your littleBits Cloud module to every thing on the internet!
About Wireless Tag
Wireless Sensor Tag monitors and records motion events, temperature, humidity, ambient light, water leaks and can be used to find keys through beeps.
Wireless Sensor Tag monitors and records motion events, temperature, humidity, ambient light, water leaks and can be used to find keys through beeps.