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 (e.g., Condition steps) to branch logic based on the presence of the tag.