Links
Comment on page

Set values to variables using Trigger

Want to personalise the chat or capture the details about the visitor even before the chat is initiated? This is now possible with WotNot by injecting custom variables using Trigger Block
Want to personalize chat or capture details about the visitor even before the chat is initiated? This is possible with WotNot where it allows you to inject custom variables from outside using the Trigger action block even before the chat is initiated.
The values can be anything like sending and storing the details like name of the visitor, utm parameters of where the visitor is coming from can be captured and mapped with the variables.
The values stored in these defined variables, and can later be used at any given point of time in the flow of the chat.
There are two methods in WotNot that a user can follow to parse the information into variables. They are:

Via Query Params

Using this method, you will be able to send Query Params on the domain in which the bot is hosted & you will be able to map those params in the ‘Trigger’ action block with a variable name.
Let’s say I want to store the value of utm_source and utm_medium, I can simply map these names in the 'Object path/parameter' column.
And choose the variables in which this value is to be stored.
​
​
You can add a maximum of 15 entries
​

Storing values for a WhatsApp chatbot

While using this section for a WhatsApp chatbot, you can store the payload received from the WhatsApp Business API provider.
This is helpful if you want to branch out the conversation flow based on button/text inputs from an outbound message sent.
Provider
Button input
Text input
Meta
​
entry[0].changes[0].value.messages[0].button.payload
​
entry[0].changes[0].value.messages[0].text.body
360Dialog
messages[0].button.text
messages[0].text.body
Twilio
payload.Body
payload.Body
GupShup
result.payload.payload.text
​
​

Injecting JSON in the code snippet

Using this method the user will be able to inject a JSON payload inside WotNot’s code snippet. And using the trigger action block the user will be able to map the object path with a variable.
For example,
<script src="" data-session-payload='{"name": "Charles", "phone": "8164848686"}' defer></script>
In addition to the code snippet, we have added a data-session-payload section. Adding this section with a JSON payload allows WotNot to read these values and store them in variables.
In the above example, we have passed the values of “name” and “phone”, so now to store these values, we will map these fields on the Trigger action block.
It is essential to dynamically add this data-session-payload on WotNot’s code snippet before the code snippet is fired, because WotNot only reads this data once.
To read the data again, visitors would have to refresh the page and start conversing with the bot again.