Ligantic
Docs
Tutorials
How-to guides
Reference
Explanation
Login
Free Sign Up
Docs
/
Reference
/
Flows
/
Node types
/
UX

UX - Message

Type identifier: ux:message Category: UX Operations

Description

The UX - Message node sends a notification message to users in an Experience. It supports different severity levels (success, info, warning, error) and can include dynamic content through variable interpolation. Messages are displayed as toast notifications in the user interface.

Input Handles

Handle

Data Type

Description

trigger

control

Triggers the message display.

{variable}

varies

Dynamic handles for message template variables.

Output Handles

Handle

Data Type

Description

done

control

Triggered after the message is sent.

Configuration Options

Option

Type

Default

Description

Level

"success" | "info" | "warning" | "error"

"info"

Message severity level.

Delivery Method

"toast"

"toast"

How the message is delivered.

Message Template

string or Content

-

The message content with optional variables.

Variables

string[]

-

Variable names used in the template.

Message Levels

Level

Use Case

Visual Style

success

Confirm successful actions

Green, checkmark icon

info

Informational notices

Blue, info icon

warning

Caution messages

Yellow/Orange, warning icon

error

Error notifications

Red, error icon

Behaviour

  1. Receives trigger from control flow
  2. Fills the template variables with the values from the input handles
  3. Shows the message to the user as a toast at the selected level
  4. Triggers done control flow

Variable Interpolation

Variables in the message template are replaced with actual values:

  • Reference variables using {variableName} syntax in templates
  • Variables can be strings, numbers, or complex objects
  • Content-type templates support rich formatting

Output Format

The node produces a ux:message output that Experiences render as toast notifications:

{
  "type": "ux:message",
  "level": "success",
  "deliveryMethod": "toast",
  "message": "Your order has been placed!"
}

Examples

Success Confirmation

Configuration:

  • Level: success
  • Message: "Your changes have been saved successfully."

Dynamic Message

Configuration:

  • Level: info
  • Variables: ["count", "itemName"]
  • Message: "Added {count} {itemName}(s) to your cart."

Inputs:

  • count: 3
  • itemName: "widget"

Result: "Added 3 widget(s) to your cart."

Error Notification

Configuration:

  • Level: error
  • Message: "Failed to process your request. Please try again."

Related pages

Flow - Trigger
Entry point for Flow runs. Defines the inputs that a Flow accepts and makes them available to downstream nodes. Every Flow must have exactly one trigger node.
Text - Template
Renders a rich-content template with variable substitution. Insert variables through the template editor, then connect each generated input handle to the value it should render. It generates dynamic content such as messages, emails, or prompts.
UX - Action
The UX - Action node triggers actions in the user interface of an Experience. It can navigate to different pages or Experiences, update data in the UI, trigger data refetches, or trigger file downloads. This enables Flows to control the user experience dynamically.