Use the template
1
Copy the template Flow
Save a copy of BotShield: Require Human Confirmation (Template) (Setup → Flows). It’s autolaunched and system-mode.
2
Call it before the sensitive step
In your own Flow, add the copy as a subflow just before the action you want gated. Pass the inputs: the linked person’s opaque ID, a plain-language action summary, a category, and the source record ID.
3
Branch on the verdict
The subflow returns
confirmed (true only on an Approved verdict), the verdict itself, the requestId, and the resolution record ID. Add a Decision after it: proceed only when confirmed is true; otherwise stop, notify, or route for review.How the pause works
Under the hood the template proposes the action, then pauses on theBotShield_Resolution_Event__e platform event filtered to this request. When the human decides in their BotShield app, BotShield pushes the resolution into your org, the event fires, and the Flow resumes exactly where it paused — with the signed verdict. No polling loops, no waiting screens.
Because the Flow pauses on an event (not a screen), it works for background automations, not just interactive ones. The pause needs an autolaunched or scheduled parent Flow: call the template from one of those, not directly from a record-triggered Flow.
Example: refund approval
A cancellation-with-refund Flow calls the subflow with “Refund booking #1042 — $168.45”, pauses, and asks the linked manager on their phone. Whenconfirmed is true, the Flow resumes and issues the refund; on a Deny or an expiry, it routes the case for manual review. The Coral Cloud demo repo includes this exact pattern.
The same confirmation for agents
Require human confirmation from an Agentforce agent instead of a Flow.
