The Configuration option, located in the Side Navigation Menu below CONFIGURATION, allows you to access global system settings in Flows. Here you can manage key aspects such as authentication keys, integrations with other platforms, Flow versions, and critical configuration operations.
In this section, you configure how the Flow handles file attachments. You can enable or disable file support and define the conditions that files must meet to be accepted.
You can specify constraints such as the maximum number of files per message, the maximum file size, and the allowed file extensions. These settings determine which files are accepted and processed within the Flow.
You can also enable the Protected flow option to require authentication before interacting with the Flow in supported channels. When enabled, consumers must log in before sending messages, ensuring that access to the Flow is restricted to authenticated consumers.
In this section, you generate and manage authentication keys used to connect the Flow with external environments.
Clicking on Generate key creates a new application key.
You can create two types of keys:
- API keys: allows you to interact programmatically with the Flow through the Chat API.
- Web keys: allows you to embed the chat window into external Web pages.
Each key type defines how the Flow is exposed and consumed.
Here you can configure connections with other platforms and services. Available options for Flow integration include Slack, Whatsapp Client, Whatsapp Client via B2Chat, and B2Chat. To add a new integration, click on Add Integration. This allows you to extend the Flow's reach by connecting it with tools that consumers already use.
In this section, you can view and manage active conversation contexts generated by the Flow. Each context represents a unique interaction session created when a consumer starts a conversation through a channel such as Web, WhatsApp, Teams, among others.
A context is associated with a specific combination of consumer, Channel, and Session ID. It acts as the execution space where variables and intermediate data are stored during the Flow.
For example, if a consumer provides their name during an interaction, that value is stored within the context and remains available for subsequent steps in the same session.
The list displays information such as Username, Session ID, Channel, and Last usage. You can use the All Channels filter to display contexts for a specific channel.
You can use this section to monitor ongoing sessions and delete contexts when needed. Deleting a context removes its stored data and resets the interaction for that consumer.
This section allows you to manage and track different versions of the Flow. Every time a flow is updated, a Snapshot can be created to maintain a history of changes. This facilitates version management and allows you to return to a previous version if necessary. The list displays versions with the Flow name, description, author, and creation date.
The Danger Zone is a critical section where you manage Flow configurations and perform irreversible operations.
You can import, export, or restore Flow configurations using a .json file. The Export option allows you to download the current configuration as a backup, while Import allows you to upload a configuration file to replace the current setup.
This section also allows you to delete all existing contexts associated with the Flow. This action removes all active sessions and stored interaction data.
Use these options with caution, as changes made in this section cannot be undone.