Actions23
- Chat Actions
- Callback Actions
- File Actions
- Message Actions
Overview
The "Send Sticker" operation of the Telegram node allows users to send stickers to a specified chat or channel on Telegram. This is useful for automating interactions in Telegram chats, such as sending visual responses, reactions, or branded stickers as part of a workflow. For example, a bot could automatically send a sticker to acknowledge receipt of a user’s message or to celebrate an event.
This operation supports sending stickers either by referencing an existing file ID on Telegram servers, providing an HTTP URL to a .webp sticker file, or uploading a new sticker from binary data.
Properties
| Name | Meaning |
|---|---|
| Chat ID | Unique identifier for the target chat or username of the target channel (in the format @channelusername). Specifies where the sticker will be sent. |
| Binary File | Boolean flag indicating whether the sticker data should be taken from a binary field input. If true, the sticker is uploaded from binary data; if false, a file ID or URL string is used. |
| Input Binary Field | The name of the input binary property that contains the sticker file data to upload. Required if "Binary File" is true. |
| Sticker | The sticker to send when not using binary data. Can be a file ID of a sticker already on Telegram servers (recommended) or an HTTP URL pointing to a .webp sticker file accessible online. |
| Reply Markup | Additional interface options for the message. Options include: Force Reply, Inline Keyboard, None, Reply Keyboard, and Reply Keyboard Remove. These control how the recipient can interact with the message. |
| Force Reply | When selected under Reply Markup, forces the user to reply to the message. Includes options to show the reply interface and restrict it to specific users. |
| Inline Keyboard | Adds an inline keyboard next to the message with customizable rows and buttons. Buttons can have text labels and additional fields like callback data, URLs, payment buttons, or inline query switches. |
| Reply Keyboard | Adds a custom reply keyboard with rows of buttons. Buttons can send text messages or request contact/location information from the user. |
| Reply Keyboard Options | Options for the reply keyboard such as resizing, one-time display, and selective visibility to specific users. |
| Reply Keyboard Remove | Options to remove the custom keyboard and selectively apply removal to specific users. |
| Additional Fields | Extra optional parameters such as disabling notifications, captions, parse modes, file names (for binary uploads), message threading, and more. These allow fine-tuning of the message behavior and appearance. |
Output
The node outputs JSON data representing the response from the Telegram API after sending the sticker. This typically includes details about the sent message, such as message ID, date, chat info, and sticker metadata.
If the sticker is uploaded from binary data, the node handles the file upload process and sends the appropriate multipart form data to Telegram.
No binary output is produced by this operation since it only sends data to Telegram.
Dependencies
- Requires a valid Telegram Bot API authentication token configured in the node credentials.
- The node uses Telegram's Bot API endpoints to send stickers.
- If sending binary data, the input must contain the binary file data properly set with filename and MIME type.
- Internet access is required to send requests to Telegram servers.
Troubleshooting
- Missing File Name for Binary Upload: If uploading a sticker from binary data without specifying a file name, the node will throw an error. Ensure the binary property includes a file name or set it manually in the "File Name" additional field.
- Invalid Chat ID: Providing an incorrect or inaccessible chat ID or channel username will cause the API call to fail. Verify the chat ID or username is correct and the bot has permission to send messages there.
- Invalid Sticker File: When sending a sticker by URL or file ID, ensure the file is a valid
.webpsticker file supported by Telegram. - API Errors: Any errors returned by Telegram API (e.g., unauthorized, bad request) will be surfaced by the node. Check the error message for details and verify bot permissions and parameters.
- Binary Data Issues: If the binary data is corrupted or improperly formatted, the upload will fail. Confirm the binary data is correctly provided and encoded.