Human in the Loop Node

Pause your workflow and wait for human approval before continuing.

Overview

The Human in the Loop node pauses your workflow and waits for a person to review and either approve or reject before the flow continues. This is useful any time you need human judgment before proceeding - reviewing AI-generated content, approving refunds, validating data before sending, etc.

How It Works

1. The workflow reaches the Human in the Loop node and pauses execution.
2. A reviewer is presented with the prompt/instructions you configured, along with any data you chose to display.
3. The reviewer clicks Approve or Reject.
4. The flow continues down the corresponding output port.

If no one responds within the configured timeout, the node automatically approves or rejects based on your On Timeout setting.

Configuration

Prompt / Instructions

Tell the reviewer what they need to do. This is the message they'll see when the flow is waiting for their input.

Examples:

• "Review this email draft before sending to the customer."
• "Approve or reject this refund request for {{amount}}."
• "Check the AI-generated summary for accuracy."

Data to Display

Specify which workflow variables to show the reviewer so they have the context they need to make a decision. Use template syntax to reference variables from earlier steps.

Examples:

• {{email_body}}
• {{refund_amount}}, {{customer_name}}
• {{ai_summary}}

This field is optional. If left empty, the reviewer will only see the prompt.

Timeout

How long the node waits for a human response before taking the automatic action. Enter a number and select the unit.

• Value: Any positive number (default: 24)
• Unit: Minutes, Hours, or Days (default: Hours)

On Timeout

What happens when the timeout expires without a response:

Default is Auto-reject.

Outputs

Examples

Content Review

An AI model generates a customer email. Before sending, a human reviews and approves it.

[Model] → [Human in the Loop] → APPROVED → [Send Email]
                               → REJECTED → [Revise Draft]

Refund Approval

A customer requests a refund. The flow gathers the order details, then a manager approves or denies.

[Query Data] → [Human in the Loop] → APPROVED → [Process Refund]
                                   → REJECTED → [Send Denial Email]

Data Validation Gate

Before writing transformed data to a production database, a team member verifies the output looks correct.

[Data Mapper] → [Human in the Loop] → APPROVED → [Write Data]
                                    → REJECTED → [Log & Alert]

Tips

• Keep the Prompt clear and actionable. The reviewer should know exactly what to look for.
• Use Data to Display to surface the most relevant variables - don't make the reviewer hunt for context.
• Set a reasonable Timeout based on your use case. A refund approval might need 48 hours; a content review before a scheduled send might only get 1 hour.
• The On Timeout default is reject, which is the safer choice for most workflows. Switch to auto-approve only when the default action should be to proceed.