Botslab (Asia) to AT&T M2X integrations

Automate your workflows between Botslab (Asia) and AT&T M2X with IFTTT.

Create your own Botslab (Asia) and AT&T M2X 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.

17 triggers, queries, and actions

Doorbell is forcibly removed

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 the doorbell detects that it has been forcibly removed.

Doorbell rings

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 the doorbell detects doorbell ringing.

Human Motion 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 triggers fires every time the camera detects a motion.

Motion 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 triggers fires every time the camera detects frame change.

New datapoint

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 datapoint is written to a device.

New device location

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 the location of a device is updated.

Someone is detected lingering at the door

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 the doorbell detects someone staying at the door.

Someone is detected passing by the door

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 the doorbell detects people passing by the door.

Trigger fired

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 M2X trigger has been fired.

History of datapoints

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 datapoint is written to a device.

History of device locations

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 the location of a device is updated.

History of trigger fired

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 M2X trigger has been fired.

Send command to device

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 send a command to a specific device.

Turn 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 off a device.

Turn On

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 a device.

Update device location

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 update the location of a specific device.

Write datapoint

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 write a new datapoint to a specific device.

Doorbell is forcibly removed

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 the doorbell detects that it has been forcibly removed.

Doorbell rings

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 the doorbell detects doorbell ringing.

History of datapoints

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 datapoint is written to a device.

History of device locations

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 the location of a device is updated.

History of trigger fired

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 M2X trigger has been fired.

Human Motion 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 triggers fires every time the camera detects a motion.

Motion 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 triggers fires every time the camera detects frame change.

New datapoint

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 datapoint is written to a device.

New device location

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 the location of a device is updated.

Send command to device

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 send a command to a specific device.

Someone is detected lingering at the door

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 the doorbell detects someone staying at the door.

Someone is detected passing by the door

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 the doorbell detects people passing by the door.

Build an automation in seconds!

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

GET STARTED

How to connect to a Botslab (Asia) automation

Find an automation using Botslab (Asia)

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

Connect IFTTT to your Botslab (Asia) 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 Botslab (Asia) and AT&T M2X

About Botslab (Asia)

Botslab is a high-tech brand empowered by AI, big data, and cutting-edge loT technologies for the global market. Botslab, which stands for the laboratory of bots, is committed to providing worldwide users with reliable, smart hardware products and extraordinary user experience. Bringing the spirit of Innovation for a Smart Life, Botslab has been exploring various exciting technological products including robot vacuums, wet dry vacuums, video doorbells, indoor & outdoor smart cameras, and driving recorders.

Connect Botslab (Asia)

More integrations with Botslab (Asia)

About AT&T M2X

AT&T M2X provides time-series data storage, device management, message brokering, event triggering and data visualization for Internet of Things (IoT) products and services.

Connect AT&T M2X

More integrations with AT&T M2X