---
url: https://gudhub.com/uk/docs/automation-nodes/send-message-node/
title: "Send Message Node\n                #"
description: "Send Message is a node that allows you to send messages to users messenger. This node works together with the Conversation element and allows the user to send d"
lang: uk
updated: 2026-09-11T10:21:47.497Z
---

# Send Message Node [#](https://gudhub.com/uk/docs/automation-nodes/send-message-node/#send-message-node)

**Send Message** is a node that allows you to send messages to users messenger. This node works together with the **Conversation** element and allows the user to send data directly from the items. The most recommended gh-elements for sending messages are the [Image](https://gudhub.com/uk/docs/gh-elements/image/) and the [Text Area](https://gudhub.com/uk/docs/gh-elements/text-area/), which stores unformatted text.

> But note that the **node accepts the URL of the file**. Therefore, you need to get it first with a [File Reader](https://gudhub.com/uk/docs/automation-nodes/file-reader/).

Also, if you use this node inside an [Iterator](https://gudhub.com/uk/docs/automation-nodes/iterator-node/), you can perform bulk messaging from one specific account or bot of one of the available messengers.

![Send message node](https://bitbucket.org/AAtlas/gudhub-documentation/raw/master/Automation_Nodes/automation-nodes/send-message-node.jpg "Send message")

## Inputs [#](https://gudhub.com/uk/docs/automation-nodes/send-message-node/#inputs)

All input sockets of the current node are responsible for sending messages.

### Default Input Sockets [#](https://gudhub.com/uk/docs/automation-nodes/send-message-node/#default-input-sockets)

The input sockets of the current node are responsible for the recipient and content of the message.

> An important nuance is that a **node can send only one thing at a time**: **either a message or a file**.

If you send data to the **Message** and **File** sockets at the same time, only the data from the **Message** socket will be sent. Therefore, to avoid confusion, it is better to connect only one of these sockets at a time.

| Name | Data Type | Description |
| :-- | :-- | :-- |
| Message | `value` | _accepts the content of the email, namely the message text_ |
| Messenger User Id | `value` | _accepts the user ID from the [selected messenger](#messengers)_ |
| File | `value` | _accepts the file that have to be sent_ |

### Additional Input Sockets [#](https://gudhub.com/uk/docs/automation-nodes/send-message-node/#additional-input-sockets)

There no settings to add the additional sockets.

## Outputs [#](https://gudhub.com/uk/docs/automation-nodes/send-message-node/#outputs)

The output sockets provide the results of sending messages.

### Default Output Sockets [#](https://gudhub.com/uk/docs/automation-nodes/send-message-node/#default-output-sockets)

As already mentioned, output sockets only return the results of sending messages. Only **one socket returns a value at a time**. If the sending was successful, the **Sent** socket returns `true`. If the sending failed, the **Error** socket returns an z, for example, "Cannot read properties of undefined (reading '0')".

| Name | Data Type | Description |
| :-- | :-- | :-- |
| Sent | `value` | _returns `true` if the message was successfully sent_ |
| Error | `value` | _returns an error message_ |

### Additional Output Sockets [#](https://gudhub.com/uk/docs/automation-nodes/send-message-node/#additional-output-sockets)

This node has no additional sockets.

## Options [#](https://gudhub.com/uk/docs/automation-nodes/send-message-node/#options)

The settings of the current node are responsible for connecting to the **Conversation**. It also configures which bot from which messenger will send the message.

![Settings of the send message node](https://bitbucket.org/AAtlas/gudhub-documentation/raw/master/Automation_Nodes/automation-nodes/send-message-options.jpg "Send message options")

| Name | Description |
| :-- | :-- |
| Application | allows you to select the application in which the **Conversation** is located; [details...](#application) |
| Chat Field | allows to select the element to which the message will be sent; [details...](#chat-field) |
| Messengers | allows you to select one of the messengers configured in the **Conversation**; [details...](#messengers) |
| Notes | allows you to leave any notes in the node settings; [details...](#notes) |

### Application [#](https://gudhub.com/uk/docs/automation-nodes/send-message-node/#application)

Because the current node connects to a specific **Conversation** element, you must first select the application in which the desired element is located. Here you can select one of your applications or those to which you have [Admin access](https://gudhub.com/uk/docs/rest-api/sharing-folder/permission-policy/).

### Chat Field [#](https://gudhub.com/uk/docs/automation-nodes/send-message-node/#chat-field)

This is the setting where you have to select the **Conversation** element from the previously [selected application](#application). This is how the node will know which messenger to send messages from. That is, it is the **Conversation** element that stores this data.

This setting also provides that the sent message will be displayed in the chats of the selected element.

### Messengers [#](https://gudhub.com/uk/docs/automation-nodes/send-message-node/#messengers)

As mentioned above, the **Conversation** element contains information about messengers. So, after the preliminary settings, you can choose here the messenger from which you will send messages. Only **those messengers that are configured in the [selected element](#chat-field)** will be available here.

### Notes [#](https://gudhub.com/uk/docs/automation-nodes/send-message-node/#notes)

The last setting is common to all nodes. It allows you to save any text in the settings and it will be displayed in the node.