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

# 06.10 human tasks

# Human Tasks

Human Tasks allow a workflow to pause execution and wait for a person to review, approve, reject, or provide additional information before continuing.

This enables **human-in-the-loop** workflows, where AI automation and human judgment work together.

Human Tasks are essential for business processes that require oversight, compliance, or manual decision-making.

***

# What is a Human Task?

A Human Task temporarily pauses workflow execution.

Conceptually:

```text id="human1" theme={null}
Workflow

↓

Human Task

↓

Waiting

↓

User Decision

↓

Resume Workflow
```

The workflow remains suspended until someone completes the task.

***

# Why Use Human Tasks?

Not every decision should be made automatically.

Examples include:

* approving payments
* reviewing legal documents
* validating AI-generated content
* approving customer refunds
* reviewing security alerts
* confirming sensitive operations

Human Tasks ensure these decisions remain under human control.

***

# Workflow Lifecycle

A Human Task changes the normal execution flow.

```text id="human2" theme={null}
Workflow Running

↓

Create Human Task

↓

Pause Workflow

↓

Wait

↓

Resume

↓

Continue
```

The workflow resumes from exactly where it stopped.

***

# Human Task Object

When a Human Task node executes, it creates a task object.

A typical task contains:

* task identifier
* workflow instance identifier
* node identifier
* creation time
* completion status
* result

This information allows external systems to track and manage pending work.

***

# Waiting State

After creating the task, the workflow enters a waiting state.

```text id="human3" theme={null}
Running

↓

Waiting

↓

Completed

↓

Running
```

While waiting, no additional workflow nodes execute.

***

# Completing a Task

A user or external application completes the task.

```text id="human4" theme={null}
Open Task

↓

Approve

↓

Resume Workflow
```

The workflow executor continues from the Human Task node.

***

# Approval Example

A document approval workflow might look like this.

```text id="human5" theme={null}
Generate Contract

↓

Human Approval

↓

Approved?

↓

Continue
```

The workflow does not continue until a reviewer completes the approval.

***

# AI + Human Collaboration

Human Tasks work naturally with AI agents.

```text id="human6" theme={null}
AI Agent

↓

Draft Proposal

↓

Human Review

↓

Publish
```

The AI performs the repetitive work, while humans retain responsibility for important decisions.

***

# Workflow Context

Human Tasks may store results inside the workflow context.

Example:

```text id="human7" theme={null}
approved = True

↓

Workflow Resumes
```

Subsequent workflow nodes can use these values to determine what happens next.

***

# Forms

Human Tasks may reference forms or user interfaces.

Conceptually:

```text id="human8" theme={null}
Workflow

↓

Human Task

↓

Approval Form

↓

Submit
```

The workflow itself remains independent of the user interface implementation.

***

# Assignment

Tasks may be assigned to:

* individual users
* roles
* departments
* external systems

Assignment logic depends on the surrounding application rather than the workflow engine itself.

***

# Human Tasks vs Conditions

These components serve different purposes.

| Human Task               | Condition                    |
| ------------------------ | ---------------------------- |
| Waits for a person       | Makes an automatic decision  |
| Manual input             | Programmatic logic           |
| May take minutes or days | Executes immediately         |
| Pauses workflow          | Workflow continues instantly |

Often they are used together.

***

# Long-Running Workflows

Human Tasks make long-running workflows possible.

```text id="human9" theme={null}
Day 1

↓

Waiting

↓

Day 3

↓

Resume
```

A workflow may remain paused for minutes, hours, or even weeks.

***

# Best Practices

* Use Human Tasks only where human judgment adds value.
* Keep task descriptions clear and concise.
* Store important decisions in workflow variables.
* Separate workflow logic from user interface implementation.
* Provide meaningful task identifiers for tracking.
* Monitor outstanding tasks to avoid workflows remaining paused indefinitely.

***

# Common Use Cases

Human Tasks are commonly used for:

* approval workflows
* document review
* compliance verification
* financial authorization
* security validation
* quality assurance
* customer service escalation

***

# Summary

Human Tasks allow BindAI workflows to pause safely while waiting for manual input.

They provide the foundation for human-in-the-loop automation, combining the speed of AI with the judgment, accountability, and oversight that only people can provide.