Workflow Human Template
The Workflow Human template demonstrates how a workflow can pause execution, create a task for a human user, and resume only after that task has been completed. This pattern enables human-in-the-loop automation, where AI performs repetitive work while people remain responsible for important decisions. It is one of the most common workflow patterns used in production business systems.Purpose
This template demonstrates how to:- pause workflow execution
- create a Human Task
- wait for user input
- resume execution
- continue the workflow after approval
Workflow Structure
A typical Human Task workflow looks like this.Execution Flow
The workflow executes normally until human input is required.Creating a Human Task
When the Human Task node executes, it creates a task object. Conceptually:Waiting State
After creating the task, the workflow enters a waiting state.Example
Suppose an AI generates a purchase request.Approval Example
A common approval process looks like this.Human + AI Collaboration
Human Tasks integrate naturally with AI agents.Workflow Context
Human decisions may be stored in workflow variables. Example:Long-Running Workflows
Unlike most workflow nodes, Human Tasks may remain paused indefinitely.External Interfaces
The workflow engine is independent of the interface used to manage tasks. Possible interfaces include:- web dashboards
- mobile applications
- internal portals
- administrative tools
- external approval systems
Human Task Lifecycle
A complete lifecycle typically looks like this.Typical Use Cases
Human Tasks are commonly used for:- approval workflows
- financial authorization
- document review
- compliance verification
- AI output validation
- quality assurance
- customer escalation
- security review
Human Tasks vs Conditions
These workflow nodes solve different problems.
Many workflows combine both patterns.
Best Practices
- Use Human Tasks only where manual judgment is necessary.
- Store important decisions in workflow variables.
- Provide clear task descriptions.
- Keep workflow logic separate from user interface implementation.
- Monitor workflows waiting for long periods.
- Resume workflows only after validating task completion.
