How to retrieve contact information in a subbot

Context of enabled router

When using the context of the router, the subbot performs actions and commands on behalf of the router. In this way, the context variables, contact data, human service, analysis, resources and artificial intelligence used by the subbot will come from the router.

To activate this functionality, simply access the general settings of the subbot and enable the function.

Once the context of the router is activated in the other subbots, all data will be shared centrally, except for human service.

Practical Examples:

When using artificial intelligence, it is recommended to keep the context activated if it is necessary to use this functionality in all SubBots.
If you want to perform "Analysis" - "Custom Reports" configure it in the Router, activate the context and configure the "Event Log" in the SubBots in which you want these "Logs" to be centralized, that is, sent to the Router .
If all your contacts - "Set contacts" are centralized in one place, activate the context.
The same happens with the ​​context variables. (add the links associated with each theme)

Context of disabled router

When the router context is disabled in the subbots, contact information is not shared. Thus, it is necessary that this information is forwarded whenever there is a redirection, for such action, enable the option to send a message and fill in the context value with the contact information or other information you want to use in the subbot forwarded in JSON format.

It is important to mention that the Send message field has character limitations, so if the desired sending content is greater than the field limit, add the variable content using the Define variable action and send the variable in the field in presentation format {{VariableName}}. Once all the information has been forwarded in the redirect, just save the entry in a variable in the initial block of the forwarded subbot.

Finally, use the Define contact functionality to add user attributes based on the information saved in the variable.