[Extension] How to view and edit Builder contact variables with the Builder Variables extension October 15, 2026 21:20 Updated Introduction Features Installation and setup How to use Support Brief description: View, edit, add, and remove a chatbot's contact variables directly in the portal to test and debug Builder flows without leaving Blip. IntroductionThe Builder variables extension displays the contact variables that Builder stores for each chatbot contact and lets you manage them directly in the Blip portal. These are the same values that the flow reads and writes during the conversation (the contact's context), now gathered in a single view.For example: a customer reports that the bot greeted them with the wrong name. You search for the contact by phone number, find the name variable stored in the context, correct the value, and test the flow again, all without opening Builder.Watch a video demonstration of the extension: Features Search for a contact by phone number or ID View stored contact variables, including their names and values Edit the value of an existing variable Delete a contact variable Add a new variable to a contact Supported on the following channels: all channels on the Blip platform. Searching by phone number assumes the WhatsApp channel; to locate a contact on another channel, enter the contact's full ID. Installation and setupIn the bot whose variables you want to view, open the Blip Store and search for Builder variables. You can also open the extension directly from the Builder variables page in the Blip Store. Select the extension and click Install. Choose the bot where the extension will be used. Install it in the bot that runs the Builder flow, because that is where the contact variables are stored. Open the extension from the bot menu. The contact search screen appears. How to useSearch for a contact In the Contact ID or phone number field, enter the phone number or the contact's full ID. Click Search for contact. The extension displays the contact's ID, name, and email address (when available) and lists the stored variables. Note: the phone search automatically creates the WhatsApp identity and adds the country code 55 when you do not provide it. If the contact is not found, check the phone number (including the country code and area code) or the full ID, and verify that it belongs to the selected bot, since the same contact may be stored in another bot.View variablesAfter locating the contact, the extension lists the contact variables acquired or created while the contact moved through the flow. Each item includes the variable name and stored value, with options to edit and delete it. Values can be text, numbers, true or false, links, or JSON structures. Use this screen to check whether Builder actions are recording the contact's information as expected.When the contact has no variables, the extension displays No variables found.Edit a variableAttention: changes and deletions affect the contact's context in production immediately. Note the previous value before changing or removing a variable.Locate the variable and click the pencil icon.Enter the new value.Confirm the change. The new value is saved in the contact's context.Delete a variableLocate the variable and click the trash can icon.Confirm the deletion. The variable is removed from that contact's context.Add a new variableClick Add new variable.Fill in Variable name and Variable value. The Save button is enabled after you enter the variable name.Click Save. The new variable becomes part of the contact's context and can be used in the flow's conditions, content, and actions. SupportIf you have questions, encounter problems, or have suggestions, contact support at support@wiv.com.br. Need more help? Explore our content on Blip Academy, visit Blip Community, watch tutorials on our YouTube channel, or get your questions answered through our support channel 😃 Related articles Builder variables [Extension] How to integrate Microsoft Dynamics 365 with Blip Difference between partial match and exact match Service History How to Use Variables in Blip Desk Canned Responses