Initial concepts
So, what we can do with the Platform?
How do I know if my company needs a chatbot?
Register and login
First Steps - Creating your project
Choose your plan
Profile
Permissions system
Project Dashboard
Platform's Glossary
2-Factor Authentication
Invalid authentication code
General settings
Artificial Intelligence
Weni Brain
Zero Shot Learning
WeniGPT
What is the Weni Platform's AI Module?
Overview
What is an Intelligence?
Intents and Entities
Hands-on
Creating an Intelligence
Training your Intelligence
Intelligence Force
Tests
Inbox
Translating your dataset
Share your AI with translators
Requesting authorization
Versions
Settings
Integration
Integrate an intelligence to your project in the Weni Platform
Introducing the Content Intelligence
Integrating a Content Intelligence
Updates
Glossary
Guidelines and Good practices
Flows
Expressions and Variables Introduction
Variables Glossary
Expressions Glossary
Flows Creation
Flows introduction
Flow editor and tools
Action cards
Decision cards
Adding Media to the message
Call Webhook: Making requests to external services
Split by Intent: Using Classifiers
Import and export flows
Using expressions to capture the user's location
Viewing reports on the platform
Route markers
Studio
Contacts and Messages
Groups
Messages
Triggers and Campaigns
Adding a trigger
Triggers Types
Tell a flow to ignore triggers and keywords
Campaign introduction
How to create a Campaign
Editing events
Creating contact from an external Webhook
Contact history
How to download, extract, transform and combine archived data from Weni Flows
Channels
Settings
Channels Introduction
Adding a Facebook Channel (RapidPro)
Adding a Viber channel
How a SMS Integration Works
General API concepts and Integrations
How to create a channel on twitter
How to create a channel on Instagram
Main steps to active Whatsapp for UNICEF
Adding Discord as a channel
Creating a Slack Channel
Adding a Viber channel (RapidPro)
Creating a Microsoft Teams channel
Weni Integrations
How to use the integrations module
Adding a Web channel
Adding a Telegram channel
How to create a channel with whatsApp demo
Whatsapp: Weni Express Integration
How to create template Messages: Whatsapp
Creating a Microsoft Teams Channel
Whatsapp Business API
Integrations
Human Attendance
Weni Chats: Introduction to the Chats module
Weni Chats: Setting Up Human Attendance
Weni Chats: Human Service Dashboard
Weni Chats: Human Service Management
Weni Chats: Attendance distribution rule
Weni Chats: Using active triggering of flows
Weni Chats: CoPilot
Ticketer: Ticketer on Rapid Pro
Ticketer: How to integrate Rocket.Chat as a ticket service on the Weni Plataform
How to send message templates through RocketChat
RocketChat call routing
RCAdmin API: Agent-Activity
U-Partners - Proper use of features
Using groups to organize human attendance
Data and BI
How to Install and Use the Weni Data Connector for Power BI
Incremental Update - Power BI
Explore Weni's Database Documentation
Tips for Data Modeling in Power BI
Filter using Contact Fields in Power BI
UX Writing
- All Categories
- Flows
- Variables Glossary
Variables Glossary
Updated by Manu da Silva
Overview
Variables are places created to store values on the platform, allowing data to persist even after the completion of a flow.
To use a variable, the @
must be placed and the typed expression will be replaced by the real value of the variable, as long as it is created properly.
Below, we will make a list of how to refer to all types of variables.
Contacts and contact fields
@contact
: variables to save values directly linked to the contact. Below is a list of the most used sub-variables:@contact.name
: contact's full name;@contact.first_name
: contact's first name;@contact.urns
: list of contact's URNs. It can also be accessed through@urns
;@contact.uuid
: contact's unique id;@contact.created_on
: date when the contact was created;@contact.language
: contact's preferred language;@contact.channel
: preferred contact channel name;@contact.groups
: groups which the contact participates;;@contact.fields
: Custom contact fields. To access, just use@contact.fields.field
or@fields.field.
Results and flows
@results
: variables to saving values linked directly to the flow results. To access a result, just use@results.result_name.
Below is a list of the most used sub-variables:@results.name.category
: category / route to which that result belongs;@results.name.value
: exact result text value;@results.name.extra
: values in addition to text that a result may have, such as attachments or requisition information.
@input
: values in addition to text that a result may have, such as attachments or requisition information.@input.text
: Text value inserted by the contact in his last interaction with the platform.@input.attachments
: Attachments inserted by the contact in their last interaction with the platform.
@child
: allows referencing all child flow variables, that is, the flow that was called by the action card Enter a flow, within the parent flow. If you want to access a child flow result after its completion, for example, just use@child.results.result_name
. When using another Enter a flow chart, the@child
value is overwritten.
@parent
: allows reference to all parent flow variables, that is, the flow that called the action card Enter a flow, within the child flow. If you want to access a parent flow result during the execution of the child flow, for example, just use@parent.results.result_name.
Globals
Global variables, or globals, are variables that can be accessed from any flow, at any time, but cannot be modified during a flow execution. They are widely used when we need to send the same information to several different flows, and then we need to modify this value in a practical way for all flows where it is inserted.
To create a global one, just go to your organization's general settings and scroll down to the bottom of the page, where you will find the tab for the globals.
After that, just click on Create Global, type the name of the global you want along with the value.
It will become accessible in any flow through the variable @globals.global_name