Tag Step

The Tag step adds valuable metadata to a workflow evaluation. Tags are returned in the API response and can serve multiple purposes:

• Explain rationale: Help reviewers understand why a decision was made (e.g., “Suspicious device” or “High transaction velocity”).
• Enable automation: Provide easily parseable signals back to your backend (e.g., adverse_action_notice_required or close_account) to trigger follow-up actions.

Tags enrich evaluations with context that is visible to both reviewers and downstream systems.

Key properties

• Mandatory: Every Tag step must assign at least one tag. If you don’t need to add a tag, you don’t need the step.
• Placement: A Tag step can be used anywhere in the workflow, depending on when metadata should be attached.
• Conditions: A Tag step only sets a tag if its condition is met.
  • Use a $request is set condition (which is always true) if you always want to add a tag.
• Output field: Every Tag step creates a Boolean output field (true / false) that indicates whether the tag was set.
  • This field can be referenced in subsequent steps (for example, Condition steps) to branch logic based on the presence of the tag.

flowchart LR
    A{Condition: high velocity} -->|True| B[Tag: review_recommended]
    B --> C[Manual Review]

Configure a Tag step

1. Select the Tag step in the workflow canvas to open the side panel.
2. Select an existing tag or create a new one to assign.
3. Define the condition that must be true for the tag to be set. To always add the tag, use a $request is set condition, which is always true.
4. Review the output field. This Boolean records whether the tag was set, and downstream steps can reference it by name.
5. (Optional) Customize the Tag step's label by editing the text field at the top of the side panel.

Best practices

• Name tags for their purpose: Use clear, parseable values (for example, close_account or adverse_action_notice_required) so both reviewers and backend systems can act on them.
• Tag conditionally: Attach a meaningful condition so tags reflect real signals rather than being applied to every evaluation.
• Reuse tags downstream: Reference the Boolean output field in Condition steps to branch logic based on whether a tag was set.