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 Rule Sets — they are not supported in Monitors.

Variable Name	Description
`evaluation.outcome`	The outcome of the rule evaluation of a rule set. Includes both built-in - such as `ALLOW`, or `DENY` - as well as custom values.
`evaluation.reason`	The reason field of the rule evaluation of a rule set. This is a short, one sentence explanation of the evaluation.
`evaluation.ruleSet.name`	The name of the rule set.
`evaluation.ruleSet.uuid`	The unique identifier of the rule set.
`identifiers.accountId`	For rule sets, the account ID passed into the rule set. For monitors, the account ID from the event that triggered the condition.
`identifiers.email`	For rule sets, the email address passed into the rule set. For monitors, the email address from the event that triggered the condition.
`identifiers.deviceId`	For rule sets, the custom device ID passed into the rule set. For monitors, the custom device ID from the event that triggered the condition.
`identifiers.ip`	For rule sets, the IP address passed into the rule set. For monitors, the IP address from the event that triggered the condition.
`identifiers.paymentHash`	For rule sets, the payment hash passed into the rule set. For monitors, the payment hash from the event that triggered the condition.
`identifiers.phone`	For rule sets, the phone number passed into the rule set. For monitors, the phone number from the event that triggered the condition.
`identifiers.printId`	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).
`identifiers.timestamp`	For rule sets, the timestamp of the evaluation. For monitors, the timestamp when the triggering event was processed.
`identifiers.userAgent`	For rule sets, the browser user agent provided to the rule set. For monitors, the browser user agent from the event that triggered the condition.