> 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/chinese/guan-li-yu-she-zhi/workflow/advanced-workflow-builder/nodes.md).
# 节点
高级工作流是由边连接的**节点**构成的图。你可以从 **+ Add** 菜单中添加节点（也可以右键单击画布），并将它们连接起来以定义执行流程。
+ Add 节点菜单 — 可用的节点类型。
## 节点类型
* **Start** — 工作流的入口点。自动添加；每个流程都从这里开始。
* **When** — 触发器卡片，与标准构建器中的相同。
* **And** — 条件卡片。其结果为 true 或 false，并可据此分支流程。
* **Then** — 执行动作的卡片（设置字段、创建任务、调用 API，……）。
* **Wait ALL** — 等待所有传入分支完成后再继续。
* **Wait ANY** — 任意一个传入分支完成后立即继续。
* **OR** — 将流程分支到不同的替代路径。
* **Note** — 画布上的自由文本注释；不会影响执行。
**When / And / Then** 节点使用的卡片与 [卡片](/chinese/guan-li-yu-she-zhi/workflow/cards-overview.md) 部分所述的完全相同。
## 连接节点
节点通过**彩色边**连接。从节点**右侧**的连接手柄拖动到另一个节点**左侧**的输入手柄，即可创建连接。每种颜色表示不同的执行结果：
* **Success**（蓝色）— 节点成功完成时采用的默认路径。所有节点类型均可使用。
* **Failed Condition**（橙色）— 条件结果为 false 时采用的路径。**And**（条件）节点可使用。
* **Error**（红色）— 节点执行过程中发生错误时采用的路径。**And** 和 **Then**（动作）节点可使用。
## 执行路径高亮显示
单击任意节点即可查看其执行路径。所有通向该节点的节点以及从该节点继续延伸的节点都会高亮显示，其余内容则会变暗。对于 **Wait ALL** 节点，所有传入分支都会显示出来，让你准确查看该节点在继续之前会等待哪些分支。
## 后续步骤
* 使用 [变量](/chinese/guan-li-yu-she-zhi/workflow/advanced-workflow-builder/variables.md) 在节点之间传递数据。
* 使用 [验证与测试](/chinese/guan-li-yu-she-zhi/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 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/chinese/guan-li-yu-she-zhi/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 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.
