Skip to main content
The Chat component provides a conversational interface for AI-powered interactions. It enables real-time messaging between users and AI agents within your FlowX applications.

Overview

Real-time messaging

Send and receive messages instantly with streaming support

AI agent integration

Connect to workflows powered by AI agents

Session management

Automatic session handling and persistence across page refreshes

Customizable UI

Themeable components with independent styling for agent and user messages

Adding to a UI Flow

1

Navigate to UI Flows

Open your project and go to UI Flows from the left navigation menu.
2

Select or create a UI Flow

Select an existing UI flow or create a new one.
UI Flows
3

Open UI Assets panel

In the left sidebar, expand the UI Assets panel. Find Chat alongside Table, Collection, and other components.
UI Assets
4

Add and configure

Drag Chat onto the canvas, then configure properties in the right panel.

Configuration

Key settings

Component hierarchy

The Chat component has configurable sub-components:
Chat Component Anatomy

Settings by sub-component

The Advanced section holds an Analytics name field. Turning it on shows Analytics custom payload. An Overlay chat uses it to track when the chat is opened; an Inline chat has no analytics field. Text Input, Suggested Prompts, Voice Input, and Message Actions have their own Analytics name field.
Chat Component
Under Available actions, the New conversation and History toggles control whether the header shows the button for starting a new conversation and the button for opening past conversations.A new Chat starts with the title β€œMy chat”, the subtitle β€œYou’re chatting with an AI assistant”, and the chat icon, separator, and both available actions turned on.
Header
Searching past conversationsEnd users can search the conversation list from the history panel. Searching starts once the query is at least 3 characters long, ignoring leading and trailing spaces, and results replace the list while the query is active.
Conversation previews in the list can show raw Markdown characters such as # and * when an agent reply contains them. Rendering Markdown in the preview line is not yet supported.
Agent Message
Shown in place of an agent reply when the reply could not be generated.
Lets end users copy and rate an agent reply.
The hint text sits on the Text Input child: set Placeholder there, for example β€œAsk me anything…”. Text Input also has an Analytics name field, which tracks each message sent from the input. The message text is never sent.
Input
Text Input settings with the Placeholder field
For runtime behavior (recording limits, playback rules) see Voice input in the Chat component reference. Turning on Enable file attachments activates the File Attachments sub-component below.Turning off the input on a business conditionSelect the chat Input, then open Settings β†’ Expressions, add an expression of type Disable, and write a JavaScript condition. When it evaluates true, users can still read the conversation but cannot send a new message. The chat Input supports only the Disable expression type. See Hide and disabled conditions for how conditions behave across components.Use it to close a conversation once a journey reaches a terminal state, for example after a case is submitted or a decision is returned, while keeping the transcript readable.
Available on Web and Android. The iOS renderer does not evaluate the Disable condition yet, so on iOS the input stays enabled.
Displays pre-configured prompt suggestions before the user types. Child of Messages (alongside Agent Message and User Message).Clicking a suggestion sends it as the user’s message. Long prompts are truncated and revealed via tooltip.
Lets end users send files together with a text message. Turn on Enable file attachments on the Input sub-component to activate it, then configure the accepted files and the error copy here.Hierarchy is Chat β†’ Input β†’ File Attachments β†’ File Item. Files the user has already sent appear under Messages β†’ Attached Files β†’ File Item.
All six fields are required once file attachments are turned on. The defaults above are the runtime fallbacks the renderer applies when a field is left empty, not values the Designer fills in for you.
File Item has no properties of its own. It is the per-file row, and it carries its own default and error styling.For upload behavior, error handling, and how uploaded files reach the agent, see File attachments in the Chat component reference.

Styling

Configure visual styling through Theme Admin (Design Assets β†’ Themes β†’ Components β†’ Chat).

Themeable elements

All styling can be configured in Theme Admin for consistent branding. Changes preview in real-time.

Display modes

The Chat component has two display modes, Inline and Overlay. An Overlay chat renders as Floating, Full Screen, or both.
When adding a Chat component, the Chat Display Type dialog asks how the chat renders and where it can be placed. When you pick Overlay, select Floating, Full Screen, or both. Floating is selected by default, and at least one of the two must stay selected. A Floating chat opens from a FAB (Floating Action Button).
To change the display mode after creation, right-click the Chat and select Edit Display Types. The option appears only when the Web platform is selected.
On the Mobile device type, dropping a Chat does not open the dialog: inside a Card, Container, or Tab it is placed Inline, and anywhere else it is placed Full Screen.
Placement constraints: Inline is only available when the parent is a Container or Card. Overlay is only available when the parent is not a Container or Card. Unavailable options are disabled in the selection dialog.

Sizing defaults

For Inline, you can switch between Fill and Fixed sizing for both width and height. For Floating, width and height are fixed values you can customize in the style panel.
The sizing controls appear in the style panel only when the Web platform is selected.

Floating action button (FAB)

Floating and FullScreen modes include a Floating Action Button that triggers the chat. The FAB is configurable in the style panel:

Notification dot

When an agent replies while the chat is collapsed, a notification dot appears on the floating action button so users see there is something to read. The dot shows the number of unread agent replies, displayed as β€œ9+” above nine. It clears when the user opens the chat. Style it in the Notification dot section of the chat style panel. The values apply to both Floating and FullScreen modes.
The dot does not survive a page refresh. If a user reloads the page before opening the chat, the dot clears even though the agent reply is still unread.

Theming per display mode

Theme values are configured independently per display mode and per platform (Web, Android, iOS) through Design Assets β†’ Themes β†’ Components β†’ Chat. Supported properties include padding and margin for each mode. For complete runtime details, see the Chat component reference.

Advanced documentation

For comprehensive documentation including runtime behavior, session management, custom persistence workflows, SDK integration, and troubleshooting:

Chat component - Full reference

Complete technical documentation in AI Platform section

Chat interface concepts

High-level chat integration patterns

AI Triggers

Launch chat-driven workflows with structured trigger messages

Knowledge bases

Ground AI responses in your data

AI in FlowX

AI capabilities overview
Last modified on November 13, 2026