# Text Node

### 1. Creating a new node

* Click the **Add new node** button in the top-right corner to begin defining a new workflow element.
* From the dropdown, select **Text node**—this creates the container for your first messages.
* A blank text node will appear at the start of the canvas, acting as a placeholder for your content.
* Drag the node to any location on the canvas—its position will be saved automatically.

<figure><img src="/files/bOHT3nlAh8IVDHcWH7lP" alt=""><figcaption><p>Workflow canvas with an empty text node</p></figcaption></figure>

### 2. Adding a new message

* Inside the text node, click **Add a new message** to launch the Message Builder.
* The Message Builder interface loads, offering intuitive tools to craft and preview your content.
* Choose the message format that best suits your needs (e.g., plain text, buttons, form fields, or carousel).
* Click **Save** in the bottom-right corner to commit your message and return to the workflow canvas.

<figure><img src="/files/OcKwGANGBfIN9IRDZXBx" alt="" width="304"><figcaption><p>Text node with a message</p></figcaption></figure>

{% hint style="warning" %}
**NOTE:** You can add multiple messages of different types in the same node. However, these messages will appear **in-sequence** in the chatbot when the workflow is getting executed.
{% endhint %}

### 3. Linking to a new node

Once your message is saved, locate the handle that appears at the end of any button you added—this connector lets you define the next step in the workflow. If you haven’t added a button yet, consider doing so now to follow along with this guide and visualize the linking process.

<div><figure><img src="/files/I7y0dRBnoB6kO1wsRQZH" alt="" width="375"><figcaption><p>A text node with a button signifying a handle</p></figcaption></figure> <figure><img src="/files/rq5ow3YYDK8XTR4wmpBj" alt="" width="274"><figcaption><p>A text node with a form submit button<br>signifying a handle</p></figcaption></figure></div>

<mark style="color:yellow;">To link two steps, just click the little circle with a line on the first step, drag your cursor to the circle on the next step, and release. A line will then appear between them, letting you know they’re successfully connected.</mark>

{% hint style="info" %}
**NOTE**: Connectors linking your current **text node** to another node are only exposed on interactive elements.\
– **Text message**: connectors appear on each button expect **link button type**.\
– **Form message**: connectors are attached to the submit button.\
– **Carousel message**: connectors reside on the global navigation control, not on individual item buttons. Full support for per-item carousel connectors will be available in future releases.
{% endhint %}

### 4. Form data sharing

Values submitted through a text node’s form propagate **only to the node directly linked by that form’s submit button.** <mark style="color:yellow;">Nodes further downstream that aren’t directly connected via that submit handle will not receive the data.</mark> To inspect the shared data, Click the **eye** icon on the connector edge to open the **Shared Data** panel and review the submitted **JSON form payload**. <br>

<figure><img src="/files/ub98LeqWwuZSJDaL3TPE" alt="" width="375"><figcaption><p>Shared Data panel on an edge connected from text to any node</p></figcaption></figure>

{% hint style="warning" %}
**NOTE**: To access a form’s output in the immediately connected node, wrap the field key in double curly braces. Eg: if your form input is named `name`, include `{{data.name}}` in the next node to inject that value. Below is an attached screenshot for your reference.
{% endhint %}

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

<figure><img src="/files/nQeSiIk1lezEHsDDJGXX" alt="" width="375"><figcaption></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://orimon.gitbook.io/docs/product-guides/workflows/text-node.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
