Collect information and add human approvals
Let a playbook wait for facts, review fresh evidence, and continue with a clear decision.
Some workflows need more than a sequence of immediate actions. Use information collections and approval steps when the next action depends on an answer or a teammate’s judgment.
Ask for the missing information
Configure a playbook to ask the customer or assignee a specific question and wait for an eligible reply. The collected answer is retained as evidence for later steps.
The Collections tab also supports manual collection work. Capture the relevant response when needed, or cancel a collection that is no longer useful.
Ask for facts that change the next step, such as whether a blocker is resolved. Collecting a response alone does not mark a customer outcome successful.
Place approval where it matters
You can require approval before the first step, or add an ordered Human approval step later in the playbook. A later gate is useful after a collection or connector has produced new evidence.
In Approvals, an administrator reviews the proposed continuation and its evidence, then approves or rejects it. The playbook waits at the gate instead of carrying on while the decision is pending.
Verify before declaring success
Configure the field, operator, and target that establish success. A connector can provide an observation from another service; a verification step checks the configured result.
If verification doesn’t establish success, keep the work open or escalate with the collected context. A completed request to another service is not automatically proof that the customer reached their goal.
If a workflow stalls, inspect its collection, approval, and log state. It may be waiting for an answer rather than failing. For a failed or uncertain external action, use the playbook’s reconciliation flow instead of starting the same action again independently.