> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tryprofound.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Human Review node

> Add a step where a person approves, rejects, or edits a Workflow's output before the run continues

The Human Review node adds a review step inside a Workflow. Use it when a person needs to approve, reject, or edit a Workflow's output before the run continues.

![Human Review node settings with reviewer instructions, Content to Review, and reviewer notification controls](https://mintcdn.com/profound-37face47/krg2axnqfW1y145P/images/agents/nodes/human-review-1.png?fit=max\&auto=format\&n=krg2axnqfW1y145P\&q=85\&s=fdc37f683651d677a8f0a233afbdb6c0)

## When to use this node

Use the Human Review node for tasks such as:

* Reviewing AI-generated content before publishing
* Sending generated ads, claims, or messaging to a legal or compliance reviewer before they go live
* Approving a content brief, then generating the article from the approved version

## Limitations

* The Human Review node **works only with text or string values** and doesn't support lists, numbers, or other variable types.
* The node doesn't work with the [Iteration node](https://docs.tryprofound.com/agents/how-tos/add-iterations-to-workflows.md). However, it can run in [Sheets](https://docs.tryprofound.com/sheets/getting-started.md), and multiple Human Review nodes can run sequentially within the same Workflow.

## Configuration

### Review mode (required)

Choose what the reviewer can do:

* **Review only**: the reviewer approves or rejects the output to continue or cancel the run.
* **Review with edits**: the reviewer can edit the output before approving.

### Instructions for Reviewer (optional)

Add guidance for the person reviewing this step.

### Content to Review (required)

In the dropdown menu, select the variable that contains the content you want reviewed.

### Reviewer (required)

Choose who can review the step:

* **Any member can review**: any workspace member can respond, and the first response completes the review.
* **Current user**: only the person who runs the Workflow can review. To other team members, the Workflow appears in a waiting state.

### Review notifications (optional)

Turn on **Notify whoever started the run** for **Current user**, or **Notify everyone in your organization** for **Any member can review**. Notifications are available only when enabled for your organization.

Only published and scheduled runs send notifications. Organization notifications are grouped and may take about 15 minutes. Members who muted organization reviews don't receive them.

### Output label (required)

Enter a descriptive label for this step's output, such as `reviewed_output` or `approved_brief`, or keep the default.

## Output

The node returns the reviewed result as text. In **Review only** mode, this is the approved output. In **Review with edits** mode, this is the reviewer's edited version. The run pauses at this step until the reviewer responds, then continues on approval. On rejection, the run stops and appears as failed in **Past runs**.

## Example use case: Approve the article content before publishing it to your WordPress site

1. Add the node that generates your content, such as [Generate Article](https://docs.tryprofound.com/agents/workflows/nodes/content-creation/generate-article.md).
2. Add a **Human Review** node. In **Content to Review**, select the generated content from step 1. Set Output label to `approved_content`.
3. Add a [WordPress](https://docs.tryprofound.com/integrations/wordpress/overview.md) - Create Post node that publishes `approved_content` to your WordPress site if the changes are approved.

## Best practices

* **Place this node before publishing**. Add it before any step that publishes or applies changes, so nothing goes live without review.
* **Write clear reviewer instructions**. The reviewer may not know what the Workflow is doing. Clear instructions help them understand what's needed and respond quickly.
* **Chain Human Review nodes.** When you use **Review with edits** to request content edits from a team member, add a second Human Review node set to **Current user** so you can check the changes before handing control back to the Workflow.

## FAQ

### How do my team members know if they need to review something?

Use the notification switch under **Reviewer**, or check the Workflow run page for pending reviews.

If notifications aren't available, add a Slack, Gmail, or other messaging node before the Human Review node.

### Does a Workflow run paused for review have a timeout?

No. The run stays paused until the review is complete.

### How do I stop or cancel a paused Workflow run?

If you created the Workflow that's asking for a review, stop the run by selecting **Stop** on the published Workflow page. If you're a team member who didn't create the Workflow, cancel the run by rejecting the review (**Start Review** > **Reject**) on the published Workflow page.

### Can I request more than one person for the review?

No, each node has only one reviewer. To collect reviews from multiple team members, chain Human Review nodes sequentially.
