Approval Queue
A human approval queue where each card names the automation, the action awaiting sign off, context chips, the requester, and approve or decline actions.
A human approval queue where each card names the automation, the action awaiting sign off, context chips, the requester, and approve or decline actions.
Search blocks by description or jump to a page.
The source for every Application block is included with Basic and Pro. Pick a plan to copy the code.
Already purchased? Log in
Approval Queue is the human in the loop surface for automations that pause before a sensitive action. Each card names the automation, states the action awaiting sign off in plain words, and lists the deciding context as chips: an amount and customer for a refund, an account and term for a renewal, a count and segment for a bulk delete. An expiry timer sits in the corner of every card.
The footer of each card credits the requesting trigger with an avatar and a relative timestamp, then offers Decline and Approve actions. A closing note explains that approvals expire after 72 hours, and that expired runs are cancelled and logged in run history, so a missed decision fails safe rather than silently.
Reach for this block on an approvals inbox page or in a review drawer, wired to your automation queue. It fits any workflow where an automation should not act alone: refunds over a threshold, contract renewals, or destructive bulk operations. The context chips are the key surface; the approver decides from them without leaving the card.
A natural flow around it on an Application Pro page:
Before
After
One strong use is the automation approvals inbox. Other queue shapes:
Tip: put the deciding numbers on the card as chips; an approver who has to open the run to see the amount will hesitate, and hesitation is where queues stall.