> For the complete documentation index, see [llms.txt](https://docs.xyb.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xyb.co/xyb-console/workflow-management/building-blocks-of-a-workflow/task-and-condition-nodes.md).

# Task and Condition Nodes

Task and Condition nodes are used to add **human review** and **decision-making logic** to automated workflows.\
They allow your workflow to pause for manual verification (Task) or branch based on certain criteria (Condition).

***

### Task Node

A **Task node** creates a manual or system-assigned task during the workflow, often used for checks, approvals, or reviews.

***

#### Key Fields in the Task Node

| Field                | Description                                                          |
| -------------------- | -------------------------------------------------------------------- |
| **Task Type**        | The kind of task to create.                                          |
| **Task Priority**    | Defines urgency: `LOW`, `MEDIUM`, or `HIGH`.                         |
| **Entity Reference** | Links the task to a specific record (e.g., employee, case, request). |
| **Input Variables**  | Dynamic data passed from earlier nodes                               |
| **Task Description** | The message or instructions shown to the reviewer.                   |

***

### Condition Node

A **Condition node** evaluates one or more logical statements and routes the workflow accordingly, for example, “If this variable is true, go this way; otherwise, go that way.”

**Key Fields in the Condition Node**

| Field               | Description                          |
| ------------------- | ------------------------------------ |
| **Input Variables** | Variables available for logic checks |
| **Variable**        | The specific variable to check       |
| **Operator**        | The condition to apply               |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.xyb.co/xyb-console/workflow-management/building-blocks-of-a-workflow/task-and-condition-nodes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.