> 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/en/api-integration/endpoint-behaviors/workflow-reply-mode-retirement.md).

# Retirement of the Built-in Workflow Reply Mode

Explains the fields and endpoints that Agent API integrations must update following the retirement of the built-in workflow reply mode.

{% hint style="warning" %}
**Compatibility changes**: This page documents API changes that break existing integrations and explains how to adapt. For the current definitions of fields such as `replyMode`, see [Create a new AI assistant](https://docs.maiagent.ai/api/api-reference/ai-zhu-li#chatbots-create) and [Update an AI assistant](https://docs.maiagent.ai/api/api-reference/ai-zhu-li#chatbots-update) in the API documentation.
{% endhint %}

If your integration used built-in workflows to create Agents, check your requests for creating and updating Agents. The current API no longer provides a built-in workflow list. The workflow reply mode no longer works, and built-in workflow fields no longer control Agent settings.

## Required Integration Changes <a href="#integration-changes" id="integration-changes"></a>

1. Stop calling `GET /api/built-in-workflows/`. This route has been removed.
2. Do not send `replyMode: "workflow"` when creating or updating an Agent; this value is rejected. The modes defined for `replyMode` are `normal`, `template`, `hybrid`, and `agent`, though the modes actually available still depend on your plan. If you omit this field when creating an Agent, it defaults to `normal`; if you omit it when updating an Agent, the existing mode is retained.
3. Remove `builtInWorkflow` from requests and stop relying on this field in responses. Even if you still send this field when updating an Agent, the API ignores it and does not change the Agent's settings.

{% hint style="info" %}
This retirement applies only to MaiAgent's built-in workflow reply mode. To connect multiple Agents through an external automation service, see [External service integration](/tech/en/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/en/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.