Retirement of the Built-In Workflow Reply Mode

Explains which fields and endpoints to update in AI assistant API integrations after the built-in workflow reply mode was retired.

If your integration used built-in workflows to create AI assistants, review your create and update requests. The current API no longer provides a list of built-in workflows. The workflow reply mode is no longer valid, and the built-in workflow field no longer controls assistant settings.

Changes required for integrations

1. Stop calling GET /api/built-in-workflows/. This endpoint has been removed.

2. Do not send replyMode: "workflow" when creating or updating an assistant; the API rejects this value. The defined replyMode values are normal, template, hybrid, and agent, though availability still depends on your plan. If you omit this field when creating an assistant, it defaults to normal. If you omit it when updating an assistant, the existing mode is retained.

3. Remove builtInWorkflow from requests and stop relying on this field in responses. If you still send it when updating an assistant, the API ignores it and leaves the assistant settings unchanged.

This retirement affects only MaiAgent's built-in workflow reply mode. To connect multiple assistants through an external automation service, see External service integration.