# Variables Variables are essential for capturing and utilizing the data dynamically in the conversation. With variables, you can personalize the chat experience by being able to say “Hey Hardik!”, instead of “Hey there!”. ## Types of variables ### **Conversation variable** Used for storing temporary data that is only relevant within a single session. * Conversation variables are session-specific and do not persist * Values are reset after the conversation ends * Ideal for storing temporary inputs like selections, intermediate responses, or flow-specific data * Helps manage state within a single interaction without affecting future conversations ### Contact variable Used for storing user-specific data that persists across conversations — making it ideal for personalization and long-term context. * Contact variables persist across all conversations with the same user * Values are stored at the user (contact) level, not session level * Ideal for storing information like name, email, preferences, lead status, etc. * Can be updated anytime and the latest value is always used * Enables personalized and contextual conversations over time ### Secret variable Used for storing sensitive values, such as API keys and authentication tokens. * Secret variables are encrypted at rest — the value is never exposed in plain text. * Once a value is set, no one on the team can view it — not even admins. * The value cannot be read after it is saved. It can only be updated (replaced) with a new value. * Secret variables can only be referenced in — HTTP request, and JavaScript blocks. * Use this type for API keys, OAuth tokens, webhook secrets, or any credential that should never be visible to teammates. ## Creating variables from variables settings Under Settings > Variables, you will find all the variables in your workspace. You can click “Create” to create a new variable and provide the details like -- name, description and type.

## **Creating variables from the bot builder** In action blocks that allow you save user input like “Collect Input”, “Buttons” etc. you have the option to create a new variable.

First, you choose the type of variable, next you provide the details like name, description, type. ## Editing variables Go to Settings > Variables > Click “Edit” on the variable. You will be only allowed to edit the description and data type.

## Deleting variables Variables can only be archived and not deleted. Go to Settings > Variables and click “Archive” on the variable you want to archive.

## Using a variable You can invoke a variable by typing # to preview the variable dropdown across the bot builder.

## Data types in variables You can store the following type of data in variables:

Data type	Description
Text	Stores any text input.
Number	Stores only numeric digits from 0 to 9.
Boolean	Stores only 0, 1, true, false.
Date	Stores date formats as DD/MM/YYYY and MM/DD/YYYY
Email	Stores email addresses.
Phone	Stores phone numbers.
Regex	Stores input based on your validation rule.

## Adding default value to variables You can add a default value to the variable, so that incase there is no value present a default value can be shown to the user. To add the default value, open the bot builder canvas, and click on the variable tag. You can then enter the fallback value.

## Customizing error messages in variables You can customise error messages in variables. 1. Navigate to Settings > Variables. 2. Locate the variable with this format (Number, Boolean, Date, Email, Phone & Regex) used for validation. 3. Click "Edit" and edit the error message field. 4. Save the changes and test the flow to confirm the new error message is displayed. This allows you to replace the default *“Invalid! Please enter a valid input”* with a custom, user-friendly error message (e.g., *“Please enter a valid business email address to continue”*). ## Retrieving JSON objects from a variable If you are storing JSON objects into variables and want to refer a particular field from the JSON object, you can follow the below approach: * Create a TEXT type variable * Store the JSON object in that variable * Use # followed by your variable name and append the field you want to refer * Hit enter so the variable chip is created For example: ``` // Assume this is your JSON object [ { "account_id": "A1", "user": "John" }, { "account_id": "A2", "user": "Sara" }, { "account_id": "A3", "user": "Mike" }, { "account_id": "A4", "user": "Tina" } ] // If I want to refer to the second object i.e. account_id=A2 #name[1].account_id# ``` ## System variables offered Here are the system variables offered by default:

Variable	Description
name	Name of the visitor
email	Email of the visitor
phone	Phone number of the visitor
ip_address	IP address of the visitor
city	City detected through the IP address of the visitor
state	State detected through the IP address of the visitor
zipcode	Zipcode detected through the IP address of the visitor
country	Country detected through the IP address of the visitor
timezone	Browser timezone of the visitor
os	System OS of the visitor
referrer_url	Referrer domain to the visitor.
unsubscribed_phone_numbers	Whether the phone number is unsubscribed from outbound messaging.
utm_source	Utm source
utm_medium	Utm medium
utm_campaign	Utm campaign
utm_content	Utm content
utm_term	Utm term
browser	Browser used during the chat
contact_id
bot	Name of the bot the visitor interacted with.
browser_language	Language set in the browser.
browser	Name of the browser.
channel	Name of the channel where the chat took place.
contact_created_by	Who created the contact.
conversation_url	Link to the conversation.
country_code	ISO country code of the country where the chat originated from.
created_at	Date when the chat was created.
gcal_selected_slot_day	Selected day when booking the meeting on Google Calendar.
gcal_selected_slot_time	Selected time when booking the meeting on Google Calendar.
timezone	Timezone of the device.
url	URL of the webpage where the user is interacting with the bot.
chat_history	Includes the transcript of the conversation so far.

## Best practices for variable management * **Use descriptive names**: Choose variable names that clearly reflect the data they hold, such as "userEmail" or "orderTotal". * **Document purposefully**: Write clear descriptions that explain the variable's role within your AI agent's workflow. * **Maintain consistency**: Use a consistent naming convention for your variables to make them easily identifiable and manageable. * **Regularly review and refine**: As your AI agent evolves, revisit your variables to see if they still serve their intended purpose or need adjustments. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://help.wotnot.io/build/interface/variables.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.