Approvals
An approval is Endue stopping to ask before an agent does something irreversible. You see the exact action, with the exact arguments, before it happens.
What triggers it
Section titled “What triggers it”Every operation a connector exposes is classified by what it does to the world. Two classes always stop for you:
| Class | Examples | Gated |
|---|---|---|
| Read | Search email, list files, read a page, query a dashboard | No |
| Write | Create a document, add a row, draft an email, update a task | No |
| Send | Send an email, post to a channel, publish a post, reply to a comment, trigger a build | Yes |
| Destructive | Delete a file, delete a record, silence an alert | Yes |
The line is not “does it change something” but “can you undo it, and does it reach someone else”. Creating a draft is a write. Sending it is a send.
What you see and what happens
Section titled “What you see and what happens”The run pauses and shows the operation and the arguments it is about to use — the recipient, the subject, the body, the file, the record.
Approve and the action runs with precisely what you saw. Approving is not a general permission; it authorizes that one action with those arguments.
Reject and the action does not happen. The agent is told, and it keeps working — it will usually adapt rather than stop, for example by proposing a different draft.
Editing before approving is not supported. If the arguments are wrong, reject, and say what should change — the agent will come back with a corrected action.
Unattended runs
Section titled “Unattended runs”A routine, or any run nobody is watching, cannot ask. When an action in an unattended run needs approval, it is refused rather than left waiting.
That is deliberate: an action that silently waits for hours until someone notices it is worse than one that fails clearly. If a scheduled job needs to send something, expect it to produce a draft and tell you, rather than send on its own.
Related gates
Section titled “Related gates”Two more things pause a run for your decision, and they work the same way:
- A skill the agent does not have. It asks rather than failing; you grant or decline in the conversation.
- A question when it needs information only you have.
Limits
Section titled “Limits”- Approvals are answered in the conversation. The inbox notifies you that one is waiting.
- You cannot edit the arguments at the gate — reject and redirect instead.
- Approval covers one action. The next send in the same run asks again.
- A rejected action cannot be replayed later; the agent must propose it again.