Difference between revisions of "Actions"
| Line 36: | Line 36: | ||
[[Action: Ambient Display|Ambient Display]] | [[Action: Ambient Display|Ambient Display]] | ||
| + | |||
| + | [[Action: Animation Overlay|Animation Overlay]] | ||
[[Action: Android Shortcut|Android Shortcut]] | [[Action: Android Shortcut|Android Shortcut]] | ||
| Line 46: | Line 48: | ||
[[Action: Authenticate User|Authenticate User]] | [[Action: Authenticate User|Authenticate User]] | ||
| + | |||
| + | [[Action: Array Manipulation|Array Manipulation]] | ||
[[Action: Autosync On/Off|Autosync On/Off]] | [[Action: Autosync On/Off|Autosync On/Off]] | ||
| Line 66: | Line 70: | ||
[[Action: Car Mode|Car Mode]] | [[Action: Car Mode|Car Mode]] | ||
| + | |||
| + | [[Action: Check Colour Pixel|Check Colour Pixel]] | ||
[[Action: Check Text In Screenshot|Check Text In Screenshot]] | [[Action: Check Text In Screenshot|Check Text In Screenshot]] | ||
Revision as of 22:23, 12 February 2024
An action is something your device can do when a macro runs. A macro must have at least one action to be valid.
Synchronous vs asynchronous
MacroDroid actions typically execute quickly, but certain actions like HTTP requests or shell scripts may take longer. To ensure that subsequent actions wait for these longer actions to complete before continuing, enable the 'Block next action until complete' option in the action's configuration GUI. Otherwise, the action will run asynchronously while other actions continue. In traditional programming languages, you could pass a callback function to execute after the asynchronous action is complete. This allows you to perform additional actions or work with the data returned by the asynchronous action. However, MacroDroid's inner workings are arbitrary, so there is no systematic option for this. Instead, you must rely on different workarounds.
Control flow
List of Actions
Notification LED Enable/Disable
Priority Mode / Do Not Disturb