Actions23
- Chat Actions
- Callback Actions
- File Actions
- Message Actions
Overview
The "Send Animation" operation of the Message resource in this Telegram node allows users to send animated files (such as GIFs or short videos) to a specified chat or channel on Telegram. This is useful for automating the sharing of animations in chats, channels, or groups, enhancing communication with engaging visual content.
Common scenarios include:
- Sending promotional animated content automatically to subscribers.
- Sharing reaction GIFs or animations in response to triggers or events.
- Broadcasting animated updates or alerts in group chats.
For example, you could configure the node to send an animation stored locally or accessible via URL to a specific chat ID whenever a certain workflow event occurs.
Properties
| Name | Meaning |
|---|---|
| Chat ID | Unique identifier for the target chat or username of the target channel (in the format @channelusername). Specifies where the animation will be sent. |
| Binary File | Boolean indicating whether the animation file should be taken from a binary input field instead of a URL or file ID. |
| Input Binary Field | The name of the binary property containing the animation data to upload when Binary File is true. Defaults to "data". |
| Animation | The animation to send if not using binary data. Can be a file ID of an existing animation on Telegram servers or an HTTP URL for Telegram to fetch the animation from the Internet. |
| Reply Markup | Additional interface options for the message. Options include: None, Force Reply, Inline Keyboard, Reply Keyboard, and Reply Keyboard Remove. |
| Force Reply | When selected under Reply Markup, configures whether to show the reply interface to the user and whether to apply it selectively to specific users. |
| Inline Keyboard | When selected under Reply Markup, adds an inline keyboard next to the message. You can define multiple rows and buttons with various actions such as callback data, URLs, payment buttons, or inline query switches. |
| Reply Keyboard | When selected under Reply Markup, adds a custom reply keyboard with rows and buttons that can request contact or location information from the user. |
| Reply Keyboard Options | Options for the reply keyboard such as resizing, one-time display, and selective visibility. |
| Reply Keyboard Remove | When selected under Reply Markup, requests clients to remove the custom keyboard, optionally selectively. |
| Additional Fields | Various optional parameters including: |
| - Caption | Caption text for the animation (0-1024 characters). |
| - Disable Notification | Whether to send the message silently without notification sound. |
| - Duration | Duration of the animation clip in seconds. |
| - File Name | Filename to use when uploading binary data. Required if sending binary data and the binary property does not have a filename. |
| - Height | Height of the animation/video. |
| - Parse Mode | How to parse the caption text. Options: Markdown (Legacy), MarkdownV2, HTML. Default is HTML. |
| - Message Thread ID | Identifier of the forum topic (used for messages in topics). |
| - Thumbnail | JPEG thumbnail of the animation file, less than 200 kB, max dimensions 320x320. Optional if server-side thumbnail generation is supported. |
| - Width | Width of the animation/video. |
Output
The node outputs JSON data representing the result returned by the Telegram API after sending the animation. This typically includes details about the sent message such as message ID, chat info, date, and the animation metadata.
If the animation was uploaded from binary data, the node handles the file upload accordingly but the output remains the JSON response from Telegram describing the sent message.
No binary output is produced by this operation.
Dependencies
- Requires a valid Telegram Bot API authentication token configured in n8n credentials.
- If sending binary data, the input must contain the binary file data in the specified binary property.
- Network access to Telegram API endpoints is required.
- For sending animations by URL or file ID, the Telegram servers must be able to access the provided URL or recognize the file ID.
Troubleshooting
- Missing File Name Error: When sending binary data, if the binary property does not have a filename and no filename is manually set in Additional Fields, the node will throw an error requesting a file name. To fix, ensure the binary data includes a filename or specify one explicitly.
- Invalid Chat ID: If the chat ID or channel username is incorrect or inaccessible by the bot, the API call will fail. Verify the chat ID or username is correct and the bot has permission to send messages there.
- Unsupported File Format or Size: Telegram imposes limits on animation formats and sizes. Ensure the animation complies with Telegram's requirements.
- Network Issues: Failures to reach Telegram API endpoints due to network problems will cause errors. Check connectivity and proxy settings if applicable.
- Incorrect Parse Mode: Using unsupported parse modes or invalid formatting in captions may cause message sending to fail or captions to render incorrectly.