Help Center

How to create flow to query user data in Aivo Studio?


The node allows you to store and retrieve information by conversation id. It is useful for keeping user data that will be used across the integration.

How to test this flow?

In the inject node of each example, you should replace the placeholder "value" at the msg.conversationHash property with the conversation id. This id is sent automatically in the "" property and could be retrieved placing a debug node in step node and triggering an integration using an intention in the bot window.

The following is an example of the "msg.payload.agentbot_user" property

"agentbot_user": {

"name": "John Doe",

"id": "123456789conversationIDExample123456789",

"phone": "11111111111",

"lastSessionId": "111111111",

"extra": {

"lastSessionId": "111111111"



How to use this node?

First you have to set the conversation Id.

This id comes inside the agentbot_user parameter, which in turn comes inside the msg.payload object at each integration interaction through the bot window.

This data can then be retrieved from the session-storage node using the mustache interpreter "{{variable}}" or be entered as a parameter in the "Session Id" input field.

Using the "Method" selector, we can choose between "GET" and "PUT" operations. GET is used to query all the information of the session ID passed as a parameter, while PUT is used to store data in the storage. Remember that in both cases, you must also send the same conversation id as a parameter.

It's important to keep in mind that the JSON to be stored should not exceed 1000 characters, since it has a size limit for optimization purposes and also that the key "ID" is a reserved word, therefore it cannot be placed inside the JSON object. Finally, please note that you cannot store null or empty data.


Download the flow by clicking on this link.

This website stores cookies on your computer. These cookies are used to collect information about how you interact with our website and allow us to remember you. We use this information in order to improve and customize your browsing experience and for analytics and metrics about our visitors both on this website and other media. To find out more about the cookies we use, see our Privacy Policy.

If you decline, your information won’t be tracked when you visit this website. A single cookie will be used in your browser to remember your preference not to be tracked.