The action proposal approval flow
Reviewing and approving the creates, updates, and deletes the AI proposes
Updated 2026.08.13
This page covers action proposals — what appears when you ask the AI to create, update, or delete something.
Asking alone changes nothing. You review the proposal card and approve it; only then does it take effect. This mechanism keeps an AI misjudgment from landing straight in your data.
The six proposal states
| State | Meaning |
|---|---|
| Pending approval | Waiting for review. Choose approve or reject here |
| Approved | Approved and moving to execution |
| Completed | Execution succeeded |
| Failed | Execution failed. Check the reason on the card |
| Rejected | Rejected. Nothing is applied |
| Expired | Time ran out; it can no longer be executed |
Only pending proposals can be approved or rejected. To redo something you rejected, ask again.
Approve or reject
Depending on the operation, the card shows Create, Update, or Delete — plus Reject.
- Approving executes it; on completion you'll see "Action applied"
- Rejecting applies nothing
- If execution fails, the card shows the reason
Open the created or updated data via Open record on the card.
How email drafts are handled
Creating an email draft is a proposal too. Approving it does not send the email. It only creates the draft — sending is a separate step.
When a proposal can't be created
If the target can't be identified, no proposal is created and an error is shown.
- "Select a contact with `@contact` before sending" — no recipient for the email draft
- "Select the target task with `@task:`" — no target for the update or delete
- "Enter a date in `<datetime>`" — no date/time for the meeting being created
All of these are resolved by specifying the target with a mention.