Place the review at a meaningful checkpoint
Use a human step after the workflow has gathered the context a reviewer needs, but before it performs an action that depends on a decision. Give the step a clear title and explain what the person should check or provide. A concise request reduces ambiguity and helps the reviewer respond with the value the later steps expect.
Treat this step as a deliberate pause in the run, not as a notification that continues automatically. The workflow's status indicates that it is waiting, and the waiting details identify the step. Make sure the person responsible can find the run and understands what information is required to continue.
Resume with the reviewed input
After the reviewer has made the decision, resume the waiting run with input for the human step. Downstream steps can then use that response through their configured connections and templates. Check that the response has the expected shape before allowing a consequential action to proceed.
If the review changes the workflow's assumptions, update the input or workflow design rather than submitting a placeholder just to clear the waiting state. Keep the review outcome visible in the run's context so later readers can understand why the workflow took that branch. If the decision is no longer appropriate, cancel the run instead of resuming it with misleading data.