> For the complete documentation index, see [llms.txt](https://docs.maiagent.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maiagent.ai/tech/api-integration/endpoint-behaviors/workflow-reply-mode-retirement.md).

# 內建工作流回覆模式退場

說明內建工作流回覆模式退場後，Agent API 串接需要調整的欄位與端點。

{% hint style="warning" %}
**相容性變更**：本頁記錄會讓既有串接失效的 API 變更與調整方式；`replyMode` 等欄位的現行定義見 API 文件[建立新 AI 助理](https://docs.maiagent.ai/api/api-reference/ai-zhu-li#chatbots-create)與[更新 AI 助理](https://docs.maiagent.ai/api/api-reference/ai-zhu-li#chatbots-update)。
{% endhint %}

如果整合程式曾用內建工作流建立 Agent，請檢查建立與更新 Agent 的請求。現行 API 不再提供內建工作流列表；工作流回覆模式已失效，內建工作流欄位也不再控制 Agent 設定。

## 串接端需要調整的地方 <a href="#integration-changes" id="integration-changes"></a>

1. 停止呼叫 `GET /api/built-in-workflows/`。此路由已移除。
2. 建立或更新 Agent 時，不要傳入 `replyMode: "workflow"`；此值會被拒絕。`replyMode` 定義的模式為 `normal`、`template`、`hybrid`、`agent`，實際可用模式仍受方案限制。建立 Agent 時若省略此欄位，預設為 `normal`；更新 Agent 時若省略，原模式會保留。
3. 從請求中移除 `builtInWorkflow`，並停止依賴回應中的這個欄位。更新 Agent 時即使仍傳入此欄位，API 也會忽略，不會變更 Agent 設定。

{% hint style="info" %}
這項退場只涉及 MaiAgent 內建工作流回覆模式。透過外部自動化服務串接多個 Agent 的做法，請參考[外部服務串接](/tech/api-integration/n8n.md)。
{% endhint %}


---

# 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.maiagent.ai/tech/api-integration/endpoint-behaviors/workflow-reply-mode-retirement.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.