Coze plugin fails to import OpenAPI 3.1, and this problem is not uncommon, especially if you just paste the ready-made interface definitions. Many people think they are just changing one or two fields, but in fact, Coze's plugin parsing is more sensitive to schema structure, and the most likely place to get stuck is the response body type.
The common error reporting in the community is very consistent: not "the interface is not usable", but "the interface documentation is not the shape Coze expects". For example, some 3.1 writing methods, empty response schemas, and overly complex joint types will be blocked directly during the import process.
Why OpenAPI 3.1 is more prone to problems
Because 3.1 is more expressive, the plugin importer may not treat all advanced writings as usable input. For users, documentation looks at specifications; For importers, it may only recognize some of the most simple structures. In the public issue, someone got stuck in a place like "Response Body only supports object types", indicating that plugin imports are not loose in their requirements for return structure.
If you want to step on the pit less, do these three things first
- Converge OpenAPI to a simpler 3.0.x style first.
- Keep the respondent body as standard as possible 'object', and don't write complex nested or empty schemas right out.
- Simplify the required fields, request body, and return body to the minimum runnable version, and then gradually add it.
A more practical way to deal with it in the community
Many people end up not "fixing Coze", but go back and organize their OpenAPI files and change them to be more conservative. The reason for this is realistic: the goal of Coze plugin imports is not to eat up all OpenAPI syntax, but to stably turn interfaces into callable plugins. The more the document is wrapped, the more likely it is to fail the import.
If you get stuck when importing, it is recommended to check whether the error is pointing to the structure, type, or field name, rather than first suspecting that the interface itself is unusable. A lot of times, it's just that the schema is too fancy and the importer doesn't want to guess.
One sentence conclusion
The failure of the Coze plugin to import OpenAPI 3.1 is mostly not due to the wrong interface being written, but rather because the document structure is too complex and the return body type is not up to par. Simplifying the schema first, the success rate is usually significantly higher.
