Keep a human on the calls that matter.
Drop a checkpoint into any workflow. The Human in the Loop node pauses the run, shows a reviewer the generated content with your instructions, and resumes only once it's approved, so nothing irreversible ships without a person's sign-off.
Approval, built into the flow.
Pause and resume
The run halts at the node and picks up exactly where it left off once a reviewer approves.
Review in context
The reviewer sees the upstream output alongside your custom instructions and acceptance criteria.
Approve or reject
Approve to pass the content downstream, or reject to branch into a fix or a fail path.
Gate irreversible steps
Sits in front of publish, send, and database writes so nothing ships unchecked.
Any content type
Text, JSON, or formatted output from any upstream node is reviewable.
Deliberate, never rushed
The workflow waits as long as it needs to; there's no timer forcing a hasty decision.
A checkpoint you drop anywhere.
Wire an upstream node's output into the Human in the Loop node, give it a name and a short instruction, and place it before the step you want to gate. When the run reaches it, execution pauses and the content is presented for review. The approved content becomes the node's output and flows on.
One decision moves the run.
Approve and the content flows to the next node unchanged. Reject and route the run into a revision loop or a fail path. Because the workflow stays paused until someone acts, every decision is deliberate. Write a specific instruction and reviews get faster and more consistent.
In front of anything that can't be undone.
Pair it with the nodes it protects: generate with an LLM, gate with Human in the Loop, then branch with a Conditional, send with the Email node, or stop with a Fail node.
Sign-off where it counts.
Content approval
Review AI-drafted articles and summaries before they publish.
Data verification
Check extracted fields before writing them to another system.
Customer messaging
Proof emails and customer-facing copy before they send.
Sensitive actions
Approve irreversible operations before they run.
Draft, review, publish.
The run pauses at review; on approval it publishes, on rejection it branches back for a fix. Nothing reaches WordPress without a human yes.
Gate it in three steps.
Place the node
Drop Human in the Loop after the step that produces content and before the step you want to gate.
Write the instruction
Add a custom message with the context and acceptance criteria so the reviewer knows exactly what to check.
Review and resume
The run pauses for approval; approve to continue or reject to branch. The approved content becomes the output.
What teams ask before they commit.
How does human-in-the-loop approval work in AI content workflows?
A human-in-the-loop checkpoint pauses an automated workflow at a defined point, shows a reviewer the generated content along with your instructions, and resumes only once it is approved. In Draft & Goal, you drop the Human in the Loop node into any workflow so nothing irreversible ships without a person's sign-off.
What does a reviewer see at a Draft & Goal approval checkpoint?
The reviewer sees the upstream output in context, alongside your custom instructions and acceptance criteria, and can review text, JSON, or formatted output from any upstream node. A specific instruction makes reviews faster and more consistent, because the reviewer knows exactly what to check before approving or rejecting.
Which workflow steps should be gated by human approval?
Anything that cannot be undone. Teams place the Draft & Goal Human in the Loop node in front of publishing, email sends, and database writes, and use it for content approval, data verification before writing to another system, customer-facing messaging, and sensitive or irreversible operations.
Does a paused workflow time out while waiting for approval?
No. The workflow waits as long as it needs to, with no timer forcing a hasty decision. The run halts at the checkpoint and picks up exactly where it left off once a reviewer approves, so every decision is deliberate rather than rushed by the automation.
What happens when a reviewer rejects content in Draft & Goal?
Approval passes the content downstream unchanged; rejection routes the run into a revision loop or a fail path you define. In a draft-review-publish workflow, for example, an approved article goes to WordPress while a rejected one branches back for edits, so nothing publishes without a human yes.
Show us the workflow.
We'll show you the 10x.
Bring the marketing workflow that eats your week. We'll build it live, with your data and your models, in 30 minutes.