Like most programming languages, Keyboard Maestro allows you to create Variables to store data for use later on in the same Macro, or in other Macros.
Variables can be set from many actions. You can set variables to specific tokenised text, to the result of a calculations, from user input, from the Keychain, by searching other variables, from the clipboard or Named Clipboards, as the result of scripts, and from many other sources.
Anywhere an Action requires a Variable, you can enter any name you like (even though often a default name is provided), as long as it conforms to these rules:
Keyboard Maestro includes variables with different breadth or scopes, in order of scope, with broadest scope first:
|Global, permanent variables|| • Accessible basically everywhere, including Scripts.
• You can also see and edit variables in the Preferences.
• You can see global variables in the Value Inspector.
|Password, semi-permanent variables|| • Name must begin or end with “PW” or “password” (case insensitive).
• Available to macros but not displayed.
• Not directly accessible via AppleScript.
• Concealed in password fields in Prompt For User Input actions.
• Not saved to disk.
|Instance Variables, local to a specific macro execution instance|| • Name must begin with “instance” (case insensitive).
• Restricted to a specific execution sequence.
• Available to the Macro where it was created and Sub-Macros of that Macro, for a given execution instance of the main macro.
• These variables are private to each execution of the same Macro, even when running simultaneously.
• Accessible by Prompt For User Input
• Accessible by scripts (when used in an Execute Script Action).
• Accessible by Custom HTML Prompt.
• Accessible by AppleScript with the
|Local Variables , local to a specific macro|| • Name must begin with “local” (case insensitive)
• Restricted to the specific Macro it is in.
• Not available to any of its Sub-Macros
• Same accessibility as Instance Variables.
Macros can create or read existing variables, which persist and are permanently stored (except Local and Instance variables which are transient, and Password variables which are never saved to disk).
Variables contain only plain, un-styled, text and may be used in any token text field in an action, as well as in Calculations in a numerical field. Variable may be used in Calculations if they contain a valid number or expression.
Global Variables are permanently stored on your Mac drive (like a file), and are available for read/write in any Macro or Action, not just the Macro where the Variable was created. These variables persist between logins and restarts of your Mac.
Variables with names that start or end with “Password” or “PW” are considered passwords – their values will not be stored (except in memory) and they cannot be read directly by shell scripts or AppleScripts, though their consequences can easily be extracted, eg with the Set Clipboard to Text action, so you should clear them as soon as they have served their purpose. The Prompt For User Input dialog will display such variables concealed in a password field.
Variables with names that start with “Instance” (case insensitive, trailing space not necessary) are considered private to a specific execution sequence. Each time the macro is run, they will start empty but their value can be seen and changed by other macros within the same execution sequence (for example, if you execute a macro using the Execute Macro action, that macro can see and change the instance variable (unless you execute it asynchronously which would create a new instance)). Since two instances of a macro can be running at the same time, this is useful to ensure they each have their own version of the variable.
Since Local and Instance variables are transient, they are not shown in the Variables preferences pane.
Variables with names that start with “Local” (case insensitive, trailing space not necessary) are considered local to a specific execution of a specific macro. Each time the macro is run, they will start empty and no other macro will see or be able to change values.
Note that Local and Instance Variables are available in scripts only when the script is called in an Execute Script action, unless you specify the execution instance explicitly.
The most direction Action to set a variable is the Set Variable to Text action.
This action processes the tokens and backslashed characters in the text and sets the variable. As will all text fields, if you wish to use another variable in the text you must use the %Variable% token, eg
The value is %Variable%VarName%.
You can also use the Set Variable to Calculation action. This action evaluates the numeric expression and then sets the variable to the result. As with all numeric fields, if you wish to use another variable in the calculation, you use the variable unadorned, eg
VarName * 3.
There are many other actions that set variables.
There are many Macro Actions that can use variables. Some of these explicitly provide for entry of the variable name, but most provide for a more general text entry that accepts either token text or a numeric expression.
When editing a field:
Variables can be used in text fields using the %Variable% token. The %Variable%
<VariableName>% token allows you to include a variable in the text,
<VariableName> is the name of the variable, and this is replaced by the value of the variable.
For Example, using the Insert Text Action:
You can also use a short form of just %Variable Name% to include variables as long as the variable exists and has a value and there is no corresponding text token, although generally it is better and clearer to use the longer form %Variable%Variable Name%.
While technically all Variables are just strings, you can access a variable as if it were an array by setting the Variable to a delimited list of text, and then using the following notation:
<VariableName>” is any valid Keyboard Maestro Variable with a delimited set of values.
,is the delimiter (see below for setting a custom delimiter).
<IndexNumber>” is an integer indicating the index (starting with 1) of the array value within the Variable Array.
%Variable%myList[3 * i + 2]%
How to Use Custom Array Delimiter
Place the custom delimiter after the closing bracket
%Variable%myList1[i]:%, where the colon
:is the delimiter used in the Variable Array.
Simple Example of Variable Array
Example of Variable Array Using a Variable for the Index
Variables can be used in calculations if their value holds a number or a numeric expression that can be evaluated. Variables are used unadorned in calculations, for example
My Variable * 7.
You can also access variables in a token field numerically using the %Calculate% token. It is important to note that calculations can contain only numeric values. When you use the %Calculate% token to reference a variable or variable array element, it will convert the element to a number.
In a Calculation field you can reference the numbers in a variable which contains a coordinate or rectangle (which is always a string, eg “100,100,200,200”) using dot notation:
|Variable.left||the left coordinate of a rectangle|
|Variable.top||the top coordinate of a rectangle|
|Variable.right||the right coordinate of a rectangle|
|Variable.bottom||the right coordinate of a rectangle|
|Variable.width||the width of a rectangle or size|
|Variable.height||the height of a rectangle or size|
|Variable.fuzz||the fuzz of an image match (rectangle,fuzz)|
|Variable.MidX||the horizontal middle of a rectangle|
|Variable.MidY||the vertical middle of a rectangle|
The Variable Name and Dot reference are case insensitive.
You can get and set Keyboard Maestro Variables (Global, Local, and Instance) in these types of scripts:
And you can generally access Keyboard Maestro variables anywhere else via AppleScript from whatever language you want to use.
"", the empty string, even when the Keyboard Maestro Engine is quit and relaunched.
"", the empty string, or until you quit the Keyboard Maestro Engine.
%Delete%does not technically delete it. It continues to exist. It is just hidden from view in all of the Variable lists and in the Preferences.
%Delete%will behave as if it does not exist in most Actions, like a If Then Else Action using a Variable Condition comparing to exists.
It may be a good idea to set a Variable to
"" if you no longer need it, or if it contains sensitive information (like a password) or a large value (like a file or web page contents).
Perhaps the best way to avoid variable clutter and eliminate sensitive and/or large values is to use either Local or Instance Variables when you do not need the Variable after completion of the Macro in which the Variable is used.
You can add a variable to an action using the Edit ➤ Insert Variable menu or Edit ➤ Insert Function ➤ Variable menu or Edit ➤ Insert Token ➤ Variable menu, or by selecting from the popup menu next to some variable fields.
Fields that expect just a variable show a small V in the field while editing it, and you can use Type Completion to complete variable names in such fields.
You can add, delete, see or change global variables in the Variables preference pane that have been created by your macros and scripts.
Local and Instance Variables are not accessible from either the Preferences Window.
You can use the Value Inspector to watch the value of a global variable.