Approval cards

An approval card is how a write reaches you before it happens. It names the app, the action and its exact inputs (the recipients, the subject, the record, the automation and its inputs) and waits.

• Approve runs exactly what the card shows, nothing else.
• Cancel runs nothing, and the agent is told.
• Answer in words: a short "yes" or "no" works like the buttons; anything longer is read as approve, reject, or a new request.

What goes on a card

• Writes in your apps: send, post, create, update, delete.
• Running, creating or deploying an automation; making or removing a schedule.
• A remote preview, a git push, switching folders.
• Saving a knowledge note.
• In a folder, writes and commands, as your permission mode says.

Up to 20 writes go on one card, so a batch is one decision. A card that says "Asks in every mode" is a destructive write. A card that says "Suggested after reading" names the outside data the turn read before proposing it.

Checks on the card

• Recipients who asked to be left out are blocked.
• Outside domains can require a card or be refused, by your organization's policy.
• Propose, don't offer: when a write is the obvious next step, the agent proposes it as a card instead of asking "should I…?" in text, so one click does it.

Durable

A pending card survives restarts of the server and of your app. A write runs once: reconnecting, retrying or answering twice never runs it again. See Reliability.