The 0.16.0 releases introduces some breaking changes in the following nodes

Conversation node : with the introduction of the concept of multi-transport, a conversation can be started with a chatId (which is the unique identifier of a user for a specific platform) or with a userId which is a generic identifier for a user. Since the chatId is specific to a platform / chatbot, a chatbot configuration is required to initiate a conversation.

All the parameters can be specified both in the configuration or in the payload of the upstream node. Read more about the multi-transport Multi-transport

Audio node , Video node , Document node , Image node all these nodes are quite similar and needed some refactoring to simplify the code and make the interface and the features similar. Now there’s a better implementation of file validation (for example some video format are accepted in Telegram but not in Facebook Messenger), nodes are able to handle local files as well as remote file (like URLs) and it’s possible to use chat context variables as file names. Since the nodes now accept not just files but also URL and context variables, the parameter name is changed, respectively in audio, image, video and document. Check the documentation of each nodes for more detail.