Skip to main content

Compatibility guide - Agentic Flow Builder

Updating workflows after the upgrade​

This page provides a summary on the required configuration on the Agentic Flow Builder. If you follow the guide and still require support, you can raise a ticket or contact the DeepOpinion team.

If you’re experiencing errors while executing your existing workflows after 21st July 2025, this may be due to the planned upgrade to the Automation Builder → Agentic Flow Builder. Certain nodes require a slight modification to its configuration to ensure compatibility and successful executions. See below for fixes to common issues you may experience:

Errors when referencing a binary file​

  • You see an error on the document Agentic Skills when referencing a binary file in a node. Check if you are using file:data to reference the file from a previous node, and change this to data.

Update the input to data

Errors with HTTP Request node​

  • You see an error when using “HTTP Request” nodes. Try removing your HTTP node, and re-adding it with the same configuration as the original. This will automatically use the latest version of the HTTP node which should resolve most issues.

Http Request node not working

Errors with return types​

  • Expressions return an object instead of an expected string. In the legacy workflow builder, objects were parsed as strings. The new builder is stricter on types, and will return an object if one was referenced. This may break your existing workflows. To fix this, you can parse the object in the expression, e.g. {{ JSON.stringify(...) }}

Object return on output

Errors with JSON to Binary node​

  • Agentic Skill for documents fail after a JSON to Binary node. This is an old node and is superseded by Convert to File node. Replacing it is recommended.

Replace old node JSON to Binarry

For support contact us at [email protected]​