Action Variables
The following table summarizes the variables available in rule action messages. Variable names must be surrounded by {{
and }}
characters.
- Variables can be used in the message body, and for email actions, in the subject line as well.
- Variables beginning with
evaluation
are available only in message-based actions within Workflows — they are not supported in Monitors.
Variable Name | Description |
---|---|
| The outcome of the rule evaluation of a workflow. Includes both built-in - such as |
| The reason field of the rule evaluation of a workflow. This is a short, one sentence explanation of the evaluation. |
| The name of the workflow. |
| The unique identifier of the workflow. |
| For workflows, the account ID passed into the workflow. For monitors, the account ID from the event that triggered the condition. |
| For workflows, the email address passed into the workflow. For monitors, the email address from the event that triggered the condition. |
| For workflows, the custom device ID passed into the workflow. For monitors, the custom device ID from the event that triggered the condition. |
| For workflows, the IP address passed into the workflow. For monitors, the IP address from the event that triggered the condition. |
| For workflows, the payment hash passed into the workflow. For monitors, the payment hash from the event that triggered the condition. |
| For workflows, the phone number passed into the workflow. For monitors, the phone number from the event that triggered the condition. |
| The Verosint SignalPrint identifier. The field may not be present unless all required identifiers are present in the rule evaluation (IP address, account ID and user agent). |
| For workflows, the timestamp of the evaluation. For monitors, the timestamp when the triggering event was processed. |
| For workflows, the browser user agent provided to the workflow. For monitors, the browser user agent from the event that triggered the condition. |
Updated 23 days ago