For the complete documentation index, see llms.txt. This page is also available as Markdown.

Telegram message

1. Overview

The Telegram Message Sending Component (identified in the interface as telegram_message) is an outbound action node focused on content transmission. Its main function is to inject emails, alerts, informational text, or media files directly into the private chat of the user interacting with the Telegram bot. It is used to guide conversations in a linear way, deliver marketing materials, or issue transactional notices without keeping the user in response validations.

2. Configuration Parameters

The block's parameters define the format and content guidelines of the message bubble that the customer will receive:

  • Message Type: Dropdown menu used to choose the category of payload that the bot will send. The mapped options include:

    • Text: Messages composed purely of plain text strings, supporting simple formatting with emojis and links.

    • Audio: Sending audio files or voice messages in formats compatible with Telegram.

    • Image: Sending graphic media, corporate banners, or promotional photos (PNG, JPG).

    • Video: Sharing audiovisual files that can be played natively in the app's player (MP4).

  • Message (* Required field if Text): The main body of the text that will be sent to the customer in the chat.

  • File URL (* Required for media): Available when the options Image, Audio or Video. Allows you to paste the file's public HTTP/HTTPS address or upload it via the Upload button.

3. Visual Builder

The graphical interface conditionally adapts its fields according to the option chosen in the parameter Message Type:

  • Simplified Text Layout: When working in Text, the interface isolates only the typing box Message, requiring the content field to be filled in (*) so that the node can be saved.

  • Advanced Media Layout: When switching to Image, the long text box is replaced by the field File URL and the purple Upload button, which allows files to be dragged directly from the flow administrator's computer to the platform's servers.

4. Special Operators

The logical properties of this component manage the interpolation of dynamic strings and asynchronous delivery processing:

  • Double-Brace Tag Interpolation: The field Message is fully compatible with inserting metadata saved in the contact using the syntax {{...}}. This allows active notifications to be personalized individually (e.g., "Your invoice is due tomorrow, {{name}}!").

  • Asynchronous Processing without Standby State: Unlike the Telegram question node, this component does not pause execution in the journey. The platform engine sends the posting request to the Telegram API servers and immediately releases the contact to the next block connected to the node.

5. Practical Examples

The table below shows classic application scenarios for this component to power conversation flows in Telegram:

Selected Message Type

File URL / Upload

Configured Content (Message)

Practical Use Case

Text

None

"Welcome to the official support channel! 🤖"

Trigger an instant initial greeting as soon as the contact activates the bot via an inbound trigger.

Image

Receipt upload.png

None

Display an explanatory infographic with the step-by-step instructions for a product immediately after the lead chooses a menu option.

Text

None

"Please wait a moment, {{name}}. We are transferring your service to the queue of the department of {{selected_department}}..."

Show a dynamic transition notice before triggering the human transfer component.

Last updated

Was this helpful?