> For the complete documentation index, see [llms.txt](https://docs.ixhello.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ixhello.com/ixhc2/flows/flow-editor/say-node.md).

# Say Node

The say node sends a message to the user and then continues to the next node. On a voice channel the *Persona* configuration of the Flow is used to create a Text-to-speech (TTS) message. 

<figure><img src="/files/wg3YS8hCM9WHMUwSzz17" alt=""><figcaption></figcaption></figure>

## Parameters

<table><thead><tr><th width="141">Setting</th><th>Description</th></tr></thead><tbody><tr><td>Message</td><td>The message to send to the user. Allows variable substitution by placing a variable name between curly brackets e.g. <code>{currentTime}</code>.</td></tr></tbody></table>

This message can contain placeholders that are substituted by variables from the flow at runtime. The placeholders are defined by a variable name within curly brackets.&#x20;

* variable `customerName = Ripley`
* Say message contains `Welcome back, {customerName}!`&#x20;
* At runtime the flow displays `Welcome back, Ripley!`.

Learn how the say node works in the [simple flow](/ixhc2/general/tutorials/build-validate-and-test-a-simple-flow.md) tutorial.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ixhello.com/ixhc2/flows/flow-editor/say-node.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.