Difference between revisions of "Actions"
Tags: Mobile web edit Mobile edit Advanced mobile edit |
(→List of Actions: Added Overlay Bar page) Tags: Mobile web edit Mobile edit |
||
| (One intermediate revision by one other user not shown) | |||
| Line 120: | Line 120: | ||
[[Action: Display Bubble Notification|Display Bubble Notification]] | [[Action: Display Bubble Notification|Display Bubble Notification]] | ||
| + | |||
| + | [[Action: Display Custom Scene|Display Custom Scene]] | ||
[[Action: Display Dialog|Display Dialog]] | [[Action: Display Dialog|Display Dialog]] | ||
| Line 230: | Line 232: | ||
[[Action: Option Dialog|Option Dialog]] | [[Action: Option Dialog|Option Dialog]] | ||
| + | |||
| + | [[Action: Overlay Bar|Overlay Bar]] | ||
[[Action: Play/Stop Sound|Play/Stop Sound]] | [[Action: Play/Stop Sound|Play/Stop Sound]] | ||
Latest revision as of 05:48, 29 July 2025
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