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

# Task

> Analyze supplied evidence, generate structured results, or classify text into named routes.

A **Task** processes its bound inputs without waiting for participant responses. Use it for grading, summaries, extraction, and classification, then use [Conversation](https://docs.livefaces.ai/workflows/nodes/conversation.md) or [Say / Message](https://docs.livefaces.ai/workflows/nodes/say-message.md) to discuss the result aloud.

## Configure

1. Select a **Provider** and **Model** available to your account.
2. Write **Instructions** describing the analysis and required result.
3. Bind every input the model needs, including a previous step's **Transcript** when analyzing dialogue.
4. Define required **Output fields** and review task limits and **Maximum time**.
5. Enable **Classification preset** when the result should choose a named route. Declare the allowed labels and connect each outcome.

The classification output label must match the declared enum. Use [Branch](https://docs.livefaces.ai/workflows/nodes/branch.md) for comparisons against values you already know.

## Outcomes

| Outcome | Meaning |
| - | - |
| `complete` | The Task returned its structured result. |
| Configured labels | With classification routing, the selected label determines the next step. |
| `error` / `timeout` | Processing failed or the execution limit was exceeded. |

## Scenario: grade an interview

Bind an interview Conversation's **Transcript** and the assessment rubric. Define outputs such as `summary`, `strengths`, and `areas_to_improve`. Instruct the Task to cite the candidate's answers and mark missing evidence as unassessed.

Connect `complete` to a feedback Conversation and bind the assessment outputs as its context. That Conversation can explain the feedback and answer follow-up questions while the Task remains responsible for the assessment.

For a routing example, classify a support issue into `billing` or `delivery` and connect each label to its own support flow.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.