About this block

Action Approval Card is the human gate that stops an assistant before it writes to your data. The card names the proposed action, update the close date on 14 open opportunities, quotes the assistant's one line rationale, then previews three sample field changes as ruled rows with the record, the field, and a struck-through before value arrowing to the new one. A link opens the remaining rows, Approve and run and Reject buttons sit below, and an expiry note gives the request 24 hours. The footer holds the line: the assistant never writes without an approval, and every approved run is logged with the exact records touched and can be reverted for 30 days.

Changes is one array and the before-and-after row makes each edit legible at a glance. Showing a sample of the real diff rather than a count is what lets an approver catch a bad rule before it runs across every record.

When to use

Reach for this block whenever an assistant proposes a bulk or destructive write, surfaced inline in the thread or in an approvals inbox. Wire Approve and run to a job that echoes back the same diff it previewed, and keep the reject path one click away.

A natural flow around it on an Application Pro page:

Before

• Agent run trace

After

• Activity feed
• Notifications panel

What you can display

One strong use is the bulk record update gate. Other approval shapes:

• Workflow step approval. An automation pausing for sign off with the payload it will send.
• Spend authorization. A proposed purchase with the line items and a budget line.
• Access request. A role change previewed as before and after permissions with an approver.

Tip: always preview a real sample of the diff, not just a count, so approvers can catch a mistake before it runs.