> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/administration-and-setup/workflow/advanced-workflow-builder/nodes.md).
# Nodes
An Advanced Workflow is a graph of **nodes** connected by edges. You add nodes from the **+ Add** menu (or right-click the canvas) and connect them to define the execution flow.
The + Add node menu — the available node types.
## Node types
* **Start** — the entry point of the workflow. Added automatically; every flow begins here.
* **When** — a trigger card, the same as in the Standard builder.
* **And** — a condition card. It evaluates to true or false and can branch the flow.
* **Then** — an action card that performs work (set fields, create tasks, call APIs, …).
* **Wait ALL** — waits until *all* incoming branches complete before continuing.
* **Wait ANY** — continues as soon as *any* incoming branch completes.
* **OR** — branches the flow down alternative paths.
* **Note** — a free-text annotation on the canvas; it does not affect execution.
The **When / And / Then** nodes use the exact same cards described in the [Cards](/administration-and-setup/workflow/cards-overview.md) section.
## Connecting nodes
Nodes are connected by **colored edges**. Drag from a handle on the **right** side of a node to the input handle on the **left** side of another node to create a connection. Each colour indicates a different execution outcome:
* **Success** (blue) — the default path taken when a node completes successfully. Available on all node types.
* **Failed Condition** (orange) — taken when a condition evaluates to false. Available on **And** (condition) nodes.
* **Error** (red) — taken when a node encounters an error during execution. Available on **And** and **Then** (action) nodes.
## Execution path highlighting
Click any node to see its execution path. All nodes leading into it and all nodes following from it are highlighted — everything else is dimmed. For **Wait ALL** nodes, every incoming branch is shown so you can see exactly what the gate waits for before continuing.
## Next steps
* Pass data between nodes with [Variables](/administration-and-setup/workflow/advanced-workflow-builder/variables.md).
* Check and run your flow with [Validation & Testing](/administration-and-setup/workflow/advanced-workflow-builder/validation-and-testing.md).
---
# 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.docbits.com/administration-and-setup/workflow/advanced-workflow-builder/nodes.md?ask=&goal=
```
`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.