Approvals & Checkpoints
Approvals
Mark a step as requiring approval, and your agent will prepare the action, then pause and wait for you — this is enforced by the platform itself, not just an instruction to the agent, so the step won't go through on its own. Approving lets the process continue automatically from where it paused; rejecting ends that run — it's marked rejected and doesn't retry on its own, so start a new run if you want to try again.
- Open the process (or the process template you're building) and mark the relevant step as requiring approval.
- When the process reaches that step, it pauses and shows up as waiting for you on the Automations page.
- Review what the agent has prepared, then Approve or Reject.
A process drafts a reply to a customer complaint but is set to require approval before sending. The agent prepares the draft and the process pauses. A team member reads the draft from the Automations page and approves it — the process resumes and sends it. If they'd rejected it instead, that run would end there, and they'd start a fresh run to try again (for example, after asking the agent to redraft it in chat).
Checkpoints
Each completed step is recorded, so a process that gets interrupted (a restart, a brief outage) resumes from its last completed step rather than starting over or losing progress.
Stopping a Process
There's currently no way to stop a process once it's running, other than rejecting it at an approval step. If you need to stop one immediately, reach out to support — in the meantime, avoid starting a process you're not ready to let run to completion (or that has no approval steps to catch it).