Node reference
Message subscribe
Listen for incoming text messages
Listen for incoming text messages
Part of Telegram / Telegram. This reference is generated from the node definitions shipped with Blokboard.
When to use it#
- Start processing when my Telegram bot receives a message.
This is an event source. It can keep listening and emit values as events arrive; stop the workflow when you want to stop listening.
Parameters#
| Parameter | Field type | Default | Description |
|---|---|---|---|
Telegram bot (connectionId) | connection | (empty) | Uses a named Telegram connection. The bot token is never stored in the workflow. |
Only this chat (chatId) | string | (empty) | Leave empty to receive text messages from every chat visible to this bot. |
On failure (onFailure) | select | stop | Choose whether a failed execution stops the workflow or only ends this path. |
Retry attempts (retryCount) | number | 0 | How many additional attempts to make after the first failure. |
Telegram bot: Select your own telegram connection. See connection setup.
Only this chat: Available under More options.
On failure: Choices: Stop workflow (stop), Continue (continue). Available under More options.
Retry attempts: Available under More options. Limits: minimum 0; no declared maximum.
Inputs#
| Port | Value | Description |
|---|---|---|
in | any |
Outputs#
| Port | Value | Description |
|---|---|---|
out | object | The next incoming Telegram text message and its metadata. |
out fields#
| Field | Type | Description |
|---|---|---|
updateId | number | |
messageId | number | |
date | string | |
text | string | |
chat.id | string | |
chat.type | string | |
chat.title | string | |
chat.username | string | |
from.id | string | |
from.isBot | boolean | |
from.username | string | |
from.firstName | string | |
from.lastName | string | |
from.languageCode | string |
Use in a workflow#
Connect this node to the path that should execute it. Run a small example, inspect its actual output, and use the expression picker to select values for later nodes.
See expressions for mapping values, workflow basics for connections, and troubleshooting for failed runs.