Actions are the fundamental building blocks of Tasker tasks. An action represents a single operation that Tasker performs, such as displaying a notification, changing a system setting, launching an application, manipulating variables, or executing code.
Tasks are composed of one or more actions that execute in sequence. Nearly every automation in Tasker ultimately consists of a series of actions.
Actions define what Tasker does when a task runs. Each action belongs to a category and may contain parameters that determine its behavior.
For example:
Turning Wi-Fi on
Setting a variable
Sending an SMS
Showing a notification
Performing a web request
Executing JavaScript
Running Java code
A task may contain a single action or hundreds of actions depending on the complexity of the automation.
Each action consists of:
The operation that Tasker will perform.
Settings and values used by the action.
Optional requirements that determine whether the action should execute.
Optional names used to identify actions for navigation and flow control.
Actions normally execute from top to bottom within a task.
Example:
1. Variable Set
2. Flash
3. Notify
In this example, Tasker performs each action in sequence.
Execution order can be modified through flow-control actions such as:
If
Else
End If
For
While
Goto
Stop
Tasker organizes actions into categories.
Actions that interact directly with the user.
Examples:
Flash
Notify
Popup
Vibrate
Beep
Actions that interact with applications.
Examples:
Launch App
Kill App
Browse URL
Actions used for scripting and logic.
Examples:
Variable Set
Variable Search Replace
Java Function
Java Code
JavaScriptlet
Run Shell
Actions that control screen behavior.
Examples:
Display Brightness
Display Timeout
Auto Rotate
Actions used for file management.
Examples:
Read File
Write File
Delete File
List Files
Actions that manipulate images.
Examples:
Load Image
Resize Image
Rotate Image
Save Image
Actions related to audio and media playback.
Examples:
Music Play
Media Control
Say
Play Ringtone
Network-related actions.
Examples:
HTTP Request
Wi-Fi
Bluetooth
Mobile Data
Actions provided by external plugins.
Examples:
AutoTools
AutoNotification
AutoVoice
Join
Actions that manipulate Tasker scenes.
Examples:
Show Scene
Hide Scene
Element Text
Element Visibility
Actions used to control task execution.
Examples:
Perform Task
Stop
Wait
Wait Until
Actions used to create and manipulate variables.
Examples:
Variable Set
Variable Add
Variable Clear
Variable Convert
Most actions support conditional execution.
Example:
Flash "Wi-Fi Enabled"
If %WIFI ~ on
The action executes only when the condition evaluates as true.
Many actions support error reporting through Tasker variables.
Common variables include:
%err
%errmsg
These variables can be used to determine whether an action succeeded or failed.
Each action category has a unique icon and color within the Tasker interface. These visual identifiers help users quickly locate actions while building tasks.
Some actions provide direct access to Android APIs and scripting environments.
Examples include:
Allows direct invocation of Android Java methods.
Executes BeanShell-based Java scripts.
Executes JavaScript code within a task.
Executes Linux shell commands.
Actions are the core components of Tasker automation. Every task, project, profile, scene interaction, and generated automation ultimately relies on actions to perform work.
Understanding actions and their categories is considered a foundational skill for Tasker users.