What can leave your workspace, and when? Anything an agent drafts for the outside world waits in Inbox until a person approves it.
What waits for approval
When an agent or automation drafts an email, a message or a change in a connected tool, Hoppflow does not run it. It places the draft in Inbox for review. A reviewer can read the draft, check the evidence behind it, edit the parts the draft allows, and then approve or reject it.
- An agent drafts an action.
- The draft waits in Inbox.
- A reviewer decides. If they reject it, nothing is sent.
- If they approve it, access is checked again. When it is still allowed, the action is sent. When the tool is no longer available, a task is created for a person instead.
Because access is checked again before sending, removing a connection or a permission in the meantime stops the action. Removing access can stop work already under way.
The approver cannot change the sending account or the kind of action. On an email, the recipients are fixed when the draft is made. An approved action is sent once, even if two people approve it at the same moment.
Approval decisions and send outcomes are kept in a tamper-evident record, so a later change to that stored record can be detected.
What skips the gate, and what never reaches it
Transactional notifications, invitations, service alerts and acknowledgements are not agent drafts. They can send without approval.
Some items are refused before they reach Inbox at all. A draft to a recipient on the do-not-contact list, or content that would send sensitive data outside the company, is stopped and nothing is queued.
Where items wait in Inbox
| Tab | What it holds |
|---|---|
| Messages | "Messages go to a person once you send them. Nothing leaves without your approval." |
| Approvals | "Approvals only change things inside your workspace." |
| Activity | "Activity is a log of what your agents did." |
Who can decide
People with Decide on approvals can decide any item in the queue. People without it still see items assigned or routed to them, items they raised, and items on projects they own.
What happens after a decision
When you approve, Hoppflow sends the action. If the tool it needs is not available, Hoppflow creates a task for a person instead, with a title such as "Connect Gmail to send: <recipient>" or "Finish approved action: <action>".
Hoppflow records a held, failed or unclear result as exactly that, never as done.
- A failed send is not retried, and the reviewer is notified.
- When the result is unclear, the item shows "Outcome unknown: check before resending". Check the destination tool before you send it again.
- A send held because the CRM could not confirm the recipient is retried automatically for up to 24 hours.
When you reject an item, the same content is not proposed again unchanged for 7 days. This applies to an identical resubmission only. A draft that was withdrawn before review does not count as a rejection.
How long an item can wait
Each pending item has a review window set by its risk. The badge on the item shows where it stands.
| Risk | Default review window |
|---|---|
| High | 24 hours |
| Medium | 72 hours |
| Low | 168 hours |
| Badge | Meaning |
|---|---|
| Due soon | Three quarters of the review window has passed. |
| Overdue | The review window has passed. |
| Escalated | The item went past its review deadline, nobody acted on it, and owners and admins were notified again. |
| Aging | The item has no review window and has waited at least 48 hours. |
When an item goes past its review deadline, Hoppflow notifies workspace owners and admins, and the assigned reviewer.