> 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/cards-overview/then/action/run-workflow.md).

# 运行工作流

<figure><img src="https://1870485400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlPczlNw8zzYNLfjfispX%2Fuploads%2Fgit-blob-2c2331f65c1c090ba0708c17f9e8ada0303c1f6e%2Fimage%20(380).png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

## 用途：

\*\*“Run Workflow”（运行工作流）\*\*卡片允许用户从可用工作流列表中动态执行选定的工作流。此卡片适用于多个工作流相互关联的自动化流程，可帮助简化操作。

## 卡片组件：

1. **Workflow（工作流）**
   * \*\*描述：\*\*指定条件评估为 true 时要执行的工作流。
   * \*\*详情：\*\*提供包含所有可用工作流的下拉列表供用户选择。

## 功能：

* \*\*条件评估：\*\*只有当 **“Where”** 和 **“And Sections”** 均评估为 true 时，卡片才会执行选定的工作流。
  * 如果任一条件为 false，则不会执行任何操作，也不会触发工作流。
* **工作流执行：**
  * 满足条件时，会自动触发指定的工作流。
  * 不满足条件时，不会执行任何工作流。

## 设置和配置：

1. **选择工作流：从可用工作流的下拉列表**中选择要触发的工作流。
2. \*\*定义条件：\*\*配置 **“Where”** 和 **“And Sections”**，指定工作流执行必须满足的条件。

## 总结：

\*\*“Run Workflow”（运行工作流）\*\*卡片提供了一种便捷高效的工作流关联方式，可轻松实现多步骤流程自动化。确保 **“Where”** 和 **“And Sections”** 中的条件均已满足后，用户即可动态执行工作流并减少人工干预。


---

# 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/cards-overview/then/action/run-workflow.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.