Create a Jira issue for each new AT&T M2X datapoint
1 ready-made AT&T M2X and Jira Applets
Turn one on, or build your own. AT&T M2X can start an automation with "New datapoint", and IFTTT can then run "Create issue" on Jira.
Automate AT&T M2X and Jira from your AI assistant
Ask Cursor to run AT&T M2X commands and log device data, right from your AI assistant, with IFTTT MCP.
Set up IFTTT MCPCreate 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
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
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.
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
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.
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.
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.
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.
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.
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.
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.
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.
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.
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
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.
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
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.
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
Issue updated
Then
Create issue
You can add delays, queries, and more actions in the next step!
GET STARTED
How to connect to a AT&T M2X automation
Find an Applet using AT&T M2X and Jira
Find an automation to connect to, or create your own!Connect IFTTT to your accounts
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 AT&T M2X and Jira
About AT&T M2X
AT&T M2X and IFTTT let you automate IoT workflows, from triggering actions when data arrives to sending commands to your connected devices.
About Jira
Jira and IFTTT let you automatically create issues and trigger actions when your projects change.