Receive an email whenever an M2X Device's Trigger is fired
How this automation works
Create a Jira issue for each new datapoint
If
New datapoint
Trigger ingredients
DeviceId
DeviceName
DeviceSerial
StreamName
Value
Timestamp
Then
Create issue
Action fields
project_and_issue_type
summary
description
You might also like...
-
83
-
-
Receive an SMS whenever an M2X Device Trigger fires
73
-
-
Create Jira issues from new Google Forms responses
24
-
Related services
Create your own AT&T M2X and Jira 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.
12 triggers, queries, and actions
Issue updated
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 issue is updated.
New datapoint
Realtime trigger
Realtime Applets run after the trigger service notifies IFTTT of a new trigger event. Since IFTTT is notified proactively of new trigger events, realtime Applets normally run within a few seconds of a trigger event occurring.
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.
New issue
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 new issue is created.
Trigger fired
Realtime trigger
Realtime Applets run after the trigger service notifies IFTTT of a new trigger event. Since IFTTT is notified proactively of new trigger events, realtime Applets normally run within a few seconds of a trigger event occurring.
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.
Create issue
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 create a new issue.
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.
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.
Create issue
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 create a new issue.
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.
Issue updated
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 issue is updated.
New datapoint
Realtime trigger
Realtime Applets run after the trigger service notifies IFTTT of a new trigger event. Since IFTTT is notified proactively of new trigger events, realtime Applets normally run within a few seconds of a trigger event occurring.
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.
New issue
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 new issue is created.
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.
Trigger fired
Realtime trigger
Realtime Applets run after the trigger service notifies IFTTT of a new trigger event. Since IFTTT is notified proactively of new trigger events, realtime Applets normally run within a few seconds of a trigger event occurring.
This Trigger fires every time a M2X trigger has been fired.
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.
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!
More on AT&T M2X and Jira
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.
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.
About Jira
The #1 software development tool used by agile teams.
The #1 software development tool used by agile teams.