Static Message Node

Send fixed, pre-defined messages with optional dynamic variables.

Overview

The Static Message Node sends a pre-configured message to the user. Unlike Agent Nodes that generate dynamic AI responses, Static Message Nodes deliver consistent, predictable content. They're perfect for confirmations, instructions, or any message that should remain the same every time.

When to Use

  • Confirmation messages after form submissions
  • Welcome or goodbye messages
  • Instructions before a form or action
  • Error messages or fallback responses
  • Legal disclaimers or terms
  • Transition messages between workflow stages

Configuration

Message Content

Enter the message text you want to send. You can use markdown formatting for rich text, lists, links, and more.

Dynamic Variables

While the message structure is static, you can insert dynamic values from previous nodes or conversation data. This allows you to personalize messages while keeping the template consistent.

Available Variables

  • Previous node responses: Data returned by earlier nodes
  • Form field values: User-submitted form data
  • Conversation context: Session information

Example

A confirmation message using form data:

Thanks, {{form.name}}! We've received your request and will contact you at {{form.email}} within 24 hours.

Example Messages

Form Submission Confirmation

"Thank you for submitting your request! Our team will review it and get back to you within 1-2 business days. Your reference number is #12345."

Pre-Form Instructions

"I'll need a few details to help you better. Please fill out the following form - it should only take about 2 minutes."

Handoff Message

"I'm connecting you with a human agent who can better assist with your request. Please hold on for a moment."

Goodbye Message

"Thanks for chatting with us today! If you have any more questions, feel free to start a new conversation anytime. Have a great day! 👋"

Best Practices

  • 1

    Keep messages concise

    Users prefer brief, clear messages over lengthy paragraphs.

  • 2

    Set expectations

    Tell users what happens next or how long they should wait.

  • 3

    Use personalization

    Include the user's name or other details to make messages feel personal.

  • 4

    Match your brand voice

    Ensure the tone is consistent with your company's communication style.

Next Steps

Action Node

Trigger external actions like emails and API calls