Human In the Loop
The Human In the Loop (HITL) node pauses a workflow and waits for a person to review, verify, or approve something before the workflow continues. This is the core human-in-the-loop (HITL) mechanism in Glacis.
When to use it
Verifying AI-extracted data before it creates a real order — "The AI extracted these line items. Are they correct?"
Approving a decision before the workflow acts on it — "Should we send this confirmation email?"
Reviewing flagged exceptions — "This order has an unusual quantity. Please check."
Compliance checkpoints — any step where a human sign-off is required by policy
How it works
The workflow reaches the Human Review step and pauses.
A task is created and assigned to the configured person or team.
The assignee reviews the data, makes any corrections, and submits their decision.
The workflow resumes with the reviewer's input available to downstream steps.
The task appears in the assignee's task list and Action Center. They can approve, reject, or modify the data before the workflow continues.
Configuration
Field | Description |
|---|---|
Assignee | Who should review — a specific person or team |
Instructions | What the reviewer needs to check or decide |
Data to review | Which fields from previous steps to show the reviewer |
Timeout | How long to wait before escalating (optional) |
What happens after review
The reviewer's decision and any modifications become available as output data for the next steps in the workflow. You can use a Condition node after Human Review to branch based on the decision — for example, proceeding if approved, or creating an escalation task if rejected.
Place Human Review after AI extraction steps for high-stakes data. The AI does the heavy lifting, and the human confirms the result — best of both worlds.
Need help?
If you have questions or run into issues, we're here to help:
Chat with us — use the support widget in the bottom-right corner of Glacis
Email — reach us at support@glacis.com
Related docs — Working with AI-Assisted Tasks | Task Types