confirm Step
The confirm step asks the user to verify information before continuing. Use it as a decision gate before sensitive actions.
Syntax
Short Form
- confirm: [order_id, shipping_address]
Full Form
- confirm:
fields: [order_id, shipping_address]
message: "Please confirm these details"
on_change:
- goto: update_details
name: "Confirm Order"
Properties
| Property | Type | Required | Description |
|---|---|---|---|
fields | string[] | Yes | Variables to confirm |
message | string | No | Custom prompt |
on_change | target | No | What happens if the user wants changes |
name | string | No | Human readable step name |
Example
- confirm:
fields: [order_id, refund_amount]
message: "Confirm refund for order {{variables.order_id}} of ${{variables.refund_amount}}"
Message-Only Checkpoints
fields may be empty when you want a checkpoint that confirms the next action rather than specific datapoints.
- confirm:
fields: []
message: "I am about to send this document for signature. Please confirm."
Card Display
Set display: card to render facts and explicit confirm/change buttons.
- confirm:
fields: [order_id, refund_amount]
message: "Review the refund before I submit it."
display: card
confirm_label: "Submit refund"
change_label: "Edit details"
Card submissions use interaction.kind = "confirm". confirm and change actions are handled deterministically and do not run LLM confirmation classification.