> 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

Configure every Advanced Workflow node type and connect success, false-condition and error routes correctly.

## Video: Nodes and routes

{% embed url="<https://docbits-videos.fra1.cdn.digitaloceanspaces.com/settings-assistant/advanced_workflows_logic/v2/en.mp4>" %}

[Captions (WebVTT)](https://docbits-videos.fra1.cdn.digitaloceanspaces.com/settings-assistant/advanced_workflows_logic/v2/en.vtt) · 1:42

<details>

<summary>Transcript (English)</summary>

Start is the manual entry. When defines an event trigger. Neither accepts incoming connections. And checks a condition. Then performs an action. Both builders share the card catalog. Notes explain the design without executing.

Drag an output to the next input. Designer blue means success, orange means false condition, and red means error. And has three outcomes. Then has success and error. Execution views show success in green.

Check whether an invoice exceeds a threshold. Connect blue to approval, orange to normal processing, and red to error handling. A false condition can continue through its connected route. It does not stop every branch.

Wait ALL joins branches. Every source must have taken a route connected to the gate. Connect both required checks and the next action. An unselected route cannot provide a required result.

Wait ANY and OR join branches when at least one source took a connected route. OR requires two different source nodes. These gates neither create exclusive choices nor cancel other actions. Test the complete graph.

Keep processing nodes reachable from an entry. Avoid cycles and incoming connections to entry nodes. Include a Then action. Validate changed routes. Imported Delay nodes need a positive duration. The current Add menu does not offer Delay.

</details>

[Watch all five chapters](/administration-and-setup/workflow/advanced-workflow-builder/videos.md)

Nodes perform work; connections carry their results to the next node. Use **+ Add** or right-click the canvas. **When**, **And** and **Then** open the card picker. Choose a category or search, select a card, then configure its fields.

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-8938741e9756d0c7ffe4e436591e4cd320dc3e09%2Fadvanced_workflows_condition_catalog_en.png?alt=media" alt="Condition card picker with category navigation, search and configurable card fields"><figcaption><p>Choose a category or search for the operation you need. The card's highlighted fields are configuration inputs.</p></figcaption></figure>

## Entry, condition and action nodes

| Node      | Purpose                                                                               | Connections                                         |
| --------- | ------------------------------------------------------------------------------------- | --------------------------------------------------- |
| **Start** | Manual entry point with a direct test control; added automatically.                   | Success output; no input.                           |
| **When**  | Event trigger. Configure the trigger card, document type and other parameters.        | Success output; no input.                           |
| **And**   | Evaluate a condition against available data.                                          | Input; success, failed-condition and error outputs. |
| **Then**  | Perform an action such as setting a field, creating a task or calling an integration. | Input; success and error outputs.                   |
| **Note**  | Explain a decision. Does not execute.                                                 | No execution connections.                           |

A manual Start test does not prove that the event-specific When path is selected during normal processing. Test the relevant trigger and its route.

### Card versions

The version pill on a card opens its available versions. A version change can change fields and behavior: review the configuration and repeat the affected tests. Prefer supported card versions with structured results. A missing-card warning means the saved card is unavailable in the current catalog, for example an unavailable partner card.

**Card version** and **Advanced Workflow type** describe different things. See the [card catalog](/administration-and-setup/workflow/cards-overview.md) for card-specific behavior.

### Document field names

Conditions and actions identify document fields by their **field names**. Input suggestions can include names from all document layouts. A suggested name is not proof that the selected document contains that field. Confirm the exact name in **Settings → Document Types → Layout Builder** and test with the relevant document type. Cards can also accept custom or runtime field names where supported.

Open **Help → Card setup** for this guidance and the link to Document Types. A display label and a field's technical name can differ.

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-518c5776c73331f783c698db8efac45a128444cd%2Fadvanced_workflows_field_names_en.png?alt=media" alt="Card setup help explaining document field names and layout-based suggestions"><figcaption><p>Verify field names against the document's layout before relying on a suggested name.</p></figcaption></figure>

## Result handles

Drag a source handle to the next node's **input**. And has two outcomes on the right and an error output below. Then has success on the right and error below.

| Designer connection           | Meaning                                                             | Example                                     |
| ----------------------------- | ------------------------------------------------------------------- | ------------------------------------------- |
| **Blue — Success**            | Operation succeeded or condition was true.                          | Amount above threshold → approval task.     |
| **Orange — Failed Condition** | Condition evaluated normally but was false. Available on And.       | Amount below threshold → normal processing. |
| **Red — Error**               | Evaluation or action could not complete. Available on And and Then. | Required data unavailable → error handling. |

Success is **blue in the designer** and **green in execution results**. Card category colors are not execution results.

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-dddbca5830f1a9a78b9ca3078d6edcb0016ecf45%2Fadvanced_workflows_connections_en.png?alt=media" alt="Built-in connection legend for blue Success, orange Failed Condition and red Error"><figcaption><p>The built-in legend distinguishes an expected false result from an execution error.</p></figcaption></figure>

If the taken result has no connection, that route has no next node. Other reachable routes can still execute. An error handler does not erase the original error from the overall result.

## Merge branches

Merge nodes combine incoming routes; they do not create branches. Connect the intended upstream **outcomes** to the gate's input, then its success output to the next action.

| Node         | Inputs                                                                       | Requirement to continue                                        |
| ------------ | ---------------------------------------------------------------------------- | -------------------------------------------------------------- |
| **Wait ALL** | At least two connections. Use distinct sources for independent requirements. | Every incoming source takes an outcome connected to this gate. |
| **Wait ANY** | At least two connections.                                                    | At least one source takes an outcome connected to this gate.   |
| **OR**       | At least two **different source nodes**.                                     | At least one source takes an outcome connected to this gate.   |

The connected handle matters. A false condition can satisfy an input when its **orange** handle is connected. A successful source does not satisfy a connection drawn from its failed-condition handle.

Several handles from one source are still one source. A matching handle can satisfy that source, but two lines do not represent independent approvals.

### Both checks are required

Connect two reachable checks to **Wait ALL**. Confirm that both sources can execute and take the connected outcomes. Joining mutually exclusive success paths can leave a required input unavailable.

### Either check is sufficient

Use **Wait ANY** or **OR** when one matching source is sufficient. Test only A matching, only B matching, neither matching and both matching. These gates are not exclusive switches and do not cancel other actions. They are not a promise that real-world approvals race and the first cancels another.

## Delay in an existing graph

The current Add menu does **not** offer Delay. An existing or imported graph can contain one. Its duration must be positive and no more than **86,400 seconds (24 hours)**. Test mode skips the actual wait; a short test runtime does not prove a production delay was ignored.

## Connection rules

* Keep processing nodes reachable from a Start or When entry.
* Include at least one Then action.
* Entry nodes cannot receive incoming connections.
* Do not connect a node to itself or create a cycle.
* Connect valid output handles to inputs.
* Meet each merge's input requirements.
* Reconnect or remove unused processing nodes; use Note for commentary.

Select a node to highlight its upstream and downstream paths, including all inputs to Wait ALL. Highlighting shows connectivity. [Tests](/administration-and-setup/workflow/advanced-workflow-builder/validation-and-testing.md) and [execution logs](/administration-and-setup/workflow/workflow-logs.md) show which paths actually ran.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.docbits.com/administration-and-setup/workflow/advanced-workflow-builder/nodes.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.