---
title: "Message Node"
slug: "message-node"
updated: 2025-12-08T16:15:47Z
published: 2025-12-09T16:46:27Z
canonical: "docs.unqork.io/message-node"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.unqork.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Message Node

![A static image displaying the Message Node](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Message%20Node.png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A36Z&se=2026-11-07T18%3A57%3A36Z&sr=c&sp=r&sig=fCEm7QMtNP4V%2BXImTGnJevALbzIKxwh8wF0D3FSMQ8o%3D)

The **Message node** sends a custom email or text message (SMS) as part of your [workflow](https://docs.unqork.io/docs/introduction-to-workflow). This feature is ideal for sending confirmations or notifications that can be styled using Nunjucks. These messages are sent using traditional email or Twilio. Twilio lets you configure your workflow to automatically send text messages. When your workflow completes, your recipient receives an email or SMS based on your selection.

Here are some real-world examples of the Message node automation:

- Confirm receipt of a submission.
- Submission approval or denial.
- Notification of missing information.

You can also use the Message node to reference any persistent data from an earlier point in the workflow. That way, you can use it as an alternative to a message-sending service like [SendGrid](https://docs.unqork.io/docs/sendgrid-in-unqork).

Here are two ways to configure this scenario:

1. Creating a workflow submission using a [Plug-In](https://docs.unqork.io/docs/plug-in-component) component. Then, you can reference that submission using a **Message** node**.**
2. Retrieving existing submission data from a schema module. Then, you can use that data to create a workflow submission and reference it with a Message node.

> [!NOTE]
> For this method to work, data must be persistent from one screen to the next in your workflow.

The Message node is never the first node in your workflow. It has an input port and an output port used to connect to other nodes. But you can have several Message nodes in a single workflow.

You'll find the Message node in the list of nodes to the left of the [Workflow Builder](https://docs.unqork.io/docs/introduction-to-workflow).

## Similar Workflow Nodes

There are various ways to send messages with a workflow. Let's take a look at how these different messaging nodes differ.

- **Message node**: Sends an email or text message to a recipient.
- [**Error node**](https://docs.unqork.io/docs/error-node): Reroutes a task in the Automated swimlane when an error occurs.
- [**Signal node**](https://docs.unqork.io/docs/signal-node): Displays a message to the end-user at a specified point in the process.

## Settings Menu Description

Let's explore the node's **Settings Menu**. This menu displays as a blue menu bar, either above or below the node, when you select the node itself. This node has these Settings Menu options:

![A static image displaying the setting menu of the Message Node.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Message%20Node%20Setting%20Menu.png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A36Z&se=2026-11-07T18%3A57%3A36Z&sr=c&sp=r&sig=fCEm7QMtNP4V%2BXImTGnJevALbzIKxwh8wF0D3FSMQ8o%3D)

| Setting | Description |
| --- | --- |
| Edit | Takes you to the Edit Message Event window, where you can configure related settings. |
| Delete | Removes the node from the workflow. |

### Edit Message Event Window Description

Click the Edit button to display the **Edit Message Event** window.

![A static image displaying the Edit Message Event setting window.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Message%20Node_Edit%20View.png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A36Z&se=2026-11-07T18%3A57%3A36Z&sr=c&sp=r&sig=fCEm7QMtNP4V%2BXImTGnJevALbzIKxwh8wF0D3FSMQ8o%3D)

| Setting | Description |
| --- | --- |
| Label | The name of your node. By default, the Label displays as `message-1`. The label you enter here is optional and displays below the node on the workflow canvas. Define your labels by associating them with the role of the node. |
| Send via | Displays the following method to send outgoing messages: - **Email**: Sends email messages from your workflow. |
| To | What to enter in the To field depends on the **Send via** selection you made. - **Send via Email**: Enter an email address for your message. For example, you can enter {{data.to}}. This is the default email address your administrator has for your specific company email. You can also manually enter an email address, like `name@domain.com`. |
| Cc | Enter the email address of your secondary recipient or the address to copy on your email. |
| Bcc | Enter the email address to blind copy on your email. |
| From Name | Enter your sender’s name here. This is a required field. |
| Reply To | Enter your sender’s email address. If you want your end-user to be able to reply to your message, enter a valid email address. If not, consider a no-reply@domain.com address. You can customize the default **From email** as part of your environment’s setup. |
| Subject | Enter a subject line for your message. This is a required field. |
| Template | Lets you set a template for the outgoing message. This template uses plain text, HTML, or Nunjucks templating language. |
| Generate and Send Refer String | When enabled, you see the Refer String TTL (Time to Live) and Refer String Redirect Target settings. If your end-user is communicating over SMS or email, there’s a chance they’re not logged into Unqork. When you enable the setting, you can send a link to your end-user. Using this link, your end-user can access Unqork. By default, the Generate and Send Refer String toggle is set to ![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/toggle_OFF.png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A36Z&se=2026-11-07T18%3A57%3A36Z&sr=c&sp=r&sig=fCEm7QMtNP4V%2BXImTGnJevALbzIKxwh8wF0D3FSMQ8o%3D) **(OFF)**. |

#### Send Via

Here, you'll see a drop-down showing available services you can use to send your message. By default, the only option you see in the Send Via field is **Email**. No other setup is needed to use this option.

> [!NOTE]
> You can only add up to 50 email addresses per workflow message node. This includes the combined total of addresses used in the To, Cc, and Bcc fields. You can organize the recipients in any way as long as it’s not more than 50 total.

To use the **Twilio** option to send an SMS, you need additional setup. You can do this under [Services Administration](https://docs.unqork.io/docs/services-administration) in your environment. Once you add a Twilio service, it displays in the **Send Via** drop-down.

> [!NOTE]
> To learn how to integrate Twilio SMS, view our [Twilio SMS Integration Template](https://docs.unqork.io/docs/twilio-sms-integration-template) article.

Once you select the service you want to use, customization fields display in these fields. You can either hardcode your own text or retrieve data from a previous screen in the workflow. Use the `{{data.fieldName}}` notation to retrieve information.

To carry this data from one screen to another, you must select **Store Data in Database** for these fields. The **Store Data in Database** setting affects how data persists through your application. You can also use the **Pass Non-Persisted Express Data to Automated Tasks** setting at the workflow level.

> [!NOTE]
> The Cc, Bcc, From Name, Reply To, and Subject settings only apply when sending an Email. The Media URL and Log this Message only apply when sending a message with Twilio.

## Adding a Message Node

Create a simple workflow with a **Start**, **Task**, **Message**, and **End** nodes to send an email. The **Task** node calls a **General Information** module, which lets your end-user submit their data. Then, the **Message** node sends a confirmation receipt email.

> These instructions assume you set up your module and have a new workflow ready.

### Configure the Start Node

1. Drag and drop a **Start** node to the **Authenticated** swimlane.
2. Click **Edit**.
3. In the **Label** field, enter `Start`.
4. Click **X** (Close).

### Configure the Task Node

Add a **Task** node to connect to your **General Information** module. Using this module, you can collect basic information from your end-user.

1. Drag and drop a **Task** node to the **Authenticated** swimlane.
2. Click **Edit**.
3. In the **Label** field, enter `General Information`.
4. From the **Module** drop-down, select the **Enablement Lab: Message Use Case- General Information** module.

[![A static image displaying the Task Node setting.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Messagte%20Node_General%20Information%20Task%20Node.png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A36Z&se=2026-11-07T18%3A57%3A36Z&sr=c&sp=r&sig=fCEm7QMtNP4V%2BXImTGnJevALbzIKxwh8wF0D3FSMQ8o%3D)](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Message%20Node%20Step4.jpg?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A36Z&se=2026-11-07T18%3A57%3A36Z&sr=c&sp=r&sig=fCEm7QMtNP4V%2BXImTGnJevALbzIKxwh8wF0D3FSMQ8o%3D)
5. Click **X** (Close).
6. Connect the output port (right) of the **Start** node to the input port (left) of the **Task** node.

### Configure the Message Node

Next, add a **Message** node to send a confirmation email to your end-user acknowledging receipt of their basic information.

1. Drag and drop a **Message** node to the **Authenticated** swimlane.

> [!NOTE]
> Position the node at the point where you need the message. In this use case, that's after the submission of an end-user's basic information. So, position your **Message Node** after the **Task Node**.
2. Click **Edit**.
3. From the **Send via** drop-down, select **Email**.
4. In the **To** field, enter `{{data.email}}`.

> [!NOTE]
> The `{{data.email}}` syntax references the value your end-user enters in the **Email** field of the **General Information** module.
5. In the **From Name** field, enter `Unqork`.
6. In the **Reply To** field, enter `no-reply@unqork.com`.
7. In the **Subject** field, enter `Your Application`.
8. In the **Template** field, enter the following:

```plaintext
Hi {{data.firstName}},

Thank you for submitting your application. We'll be in touch soon.

Regards
```

> [!NOTE]
> `{{data.firstName}}` references the value your end-user enters in the **First Name** field of the **General Information** module.

[![A static image displaying the settings of the Message Node.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Message%20Node_Email%20Setting.png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A36Z&se=2026-11-07T18%3A57%3A36Z&sr=c&sp=r&sig=fCEm7QMtNP4V%2BXImTGnJevALbzIKxwh8wF0D3FSMQ8o%3D)](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Message%20Node%20MsgNodeStep8.jpg?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A36Z&se=2026-11-07T18%3A57%3A36Z&sr=c&sp=r&sig=fCEm7QMtNP4V%2BXImTGnJevALbzIKxwh8wF0D3FSMQ8o%3D)
9. Click **X** (Close).
10. Connect the output port (right) of the `General Information` **Task** node to the input port (left) of the `message-1` **Message** node.

### Configure the End Node

1. Drag and drop an **End** node to the **Authenticated** swimlane.
2. Click **Edit**.
3. In the **Label** field, enter `End`.
4. Click **X** (Close).
5. Connect the output port (right) of the `message-1` **Message** node to the input port (left) of the `End` **End** node.
6. Click **Save...**
7. Click **Save**.

Here's how your completed workflow looks:

[![A static image displaying the Workflow for explaining the Message Node.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Message%20Node__Workflow.png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A36Z&se=2026-11-07T18%3A57%3A36Z&sr=c&sp=r&sig=fCEm7QMtNP4V%2BXImTGnJevALbzIKxwh8wF0D3FSMQ8o%3D)](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Message%20Node%20example%20complete.jpg?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A36Z&se=2026-11-07T18%3A57%3A36Z&sr=c&sp=r&sig=fCEm7QMtNP4V%2BXImTGnJevALbzIKxwh8wF0D3FSMQ8o%3D)

Preview your workflow and complete the required fields in the **General Information** module. Send the test email to yourself. After clicking **Next**, you see the `Thank you! This submission is complete.` message. Check your email account for the email.

Nunjucks is a flexible JavaScript templating engine that supports template inheritance, filters, and logic-based expressions for dynamic content rendering.

Schema is a declarative language that defines the structure, content, and constraints of the data.

End-users, also known as Express Users, are the individuals accessing an application through Express View. In most cases, end-users are the customers using the product.