Actions56
- 袙褏芯写 Actions
- 袚褉褍锌锌邪 Actions
- 袣芯薪褌邪泻褌 Actions
- 袩芯写邪褉芯泻 Actions
- 袩芯谢褜蟹芯胁邪褌械谢褜 Actions
- 袩芯谢褜蟹芯胁邪褌械谢褜褋泻懈泄 蟹邪锌褉芯褋 Actions
- 小芯芯斜褖械薪懈械 Actions
- 肖邪泄谢 Actions
- 效邪褌 Actions
- 袩芯谢褍褔懈褌褜 褋锌懈褋芯泻 锌邪锌芯泻
- 袪械写邪泻褌懈褉芯胁邪褌褜 锌邪锌泻褍
- 袛芯斜邪胁懈褌褜 褔邪褌 胁 锌邪锌泻褍
- 校写邪谢懈褌褜 褔邪褌 懈蟹 锌邪锌泻懈
- 袛芯斜邪胁懈褌褜 褍褔邪褋褌薪懈泻芯胁 胁 褔邪褌
- 袟邪泻褉褘褌褜 褔邪褌
- 袨褌泻褉褘褌褜 褔邪褌
- 袨褌屑械褌懈褌褜 褔邪褌 泻邪泻 薪械锌褉芯褔懈褌邪薪薪褘泄
- 袨褌锌褉邪胁懈褌褜 写械泄褋褌胁懈械 褔邪褌邪
- 袩芯懈褋泻 锌褍斜谢懈褔薪芯谐芯 褔邪褌邪 (锌芯 懈屑械薪懈 锌芯谢褜蟹芯胁邪褌械谢褟)
- 小芯蟹写邪褌褜 斜懈蟹薪械褋-褋褋褘谢泻褍 褔邪褌邪
- 校写邪谢懈褌褜 斜懈蟹薪械褋-褋褋褘谢泻褍 褔邪褌邪
- 袩芯懈褋泻 锌褍斜谢懈褔薪褘褏 褔邪褌芯胁 (袩芯懈褋泻 胁 懈屑械薪懈, 蟹邪谐芯谢芯胁泻械)
- 袩芯谢褍褔懈褌褜 懈薪褎芯褉屑邪褑懈褞 芯 褋褋褘谢泻械 锌褉懈谐谢邪褕械薪懈褟 胁 褔邪褌
- 袩芯谢褍褔懈褌褜 懈褋褌芯褉懈褞 褔邪褌邪
- 袩芯谢褍褔懈褌褜 锌谢邪褌薪褘械 锌芯褋褌褘 懈蟹 褔邪褌邪
- 袩芯谢褍褔懈褌褜 褍褔邪褋褌薪懈泻芯胁 褔邪褌邪, 锌褉懈褋芯械写懈薪懈胁褕懈褏褋褟 锌芯 褋褋褘谢泻械 锌褉懈谐谢邪褕械薪懈褟
- 袩芯谢褍褔懈褌褜 懈薪褎芯褉屑邪褑懈褞 芯 褔邪褌械
- 袩芯谢褍褔懈褌褜 褔邪褌褘
- 袩褉懈褋芯械写懈薪懈褌褜褋褟 泻 褔邪褌褍
- 小芯蟹写邪褌褜 褋褍锌械褉谐褉褍锌锌褍 懈谢懈 泻邪薪邪谢
- 校写邪谢懈褌褜 褔邪褌
- 袩芯谢褍褔懈褌褜 褋锌懈褋芯泻 斜懈蟹薪械褋-褋褋褘谢芯泻
- 袟胁械蟹写褘 Actions
- 袠褋褌芯褉懈懈 Actions
效邪褌 → 袩芯谢褍褔懈褌褜 褔邪褌褘
AI-generatedOverview
This node integrates with Telegram via the TelePilot API, enabling users to perform various Telegram operations programmatically. Specifically, for the resource '效邪褌' (Chat) and operation '袩芯谢褍褔懈褌褜 褔邪褌褘' (Send Message), it allows sending different types of messages such as text, photo, video, audio, files, and video notes to Telegram chats. It supports replying to messages, sending messages in threads, and setting self-destruct timers for messages. This node is useful for automating Telegram messaging workflows, such as sending notifications, media, or automated responses in chats or groups.
Use Case Examples
- Sending a text message to a Telegram chat to notify users about an event.
- Automating the sending of photos or videos to a Telegram group for marketing or updates.
- Forwarding audio messages or voice notes to a chat as part of a customer support workflow.
Properties
| Name | Meaning |
|---|---|
| chat_id | The unique identifier of the Telegram chat where the message will be sent. |
| messageText | The text content of the message to be sent. |
| reply_to_msg_id | The message ID to which the new message is replying, if any. |
| message_thread_id | The thread ID within the chat where the message should be sent, if applicable. |
| localFilePath | The local file path for sending photos or video notes. |
| videoFilePath | The local file path for sending video messages. |
| filePath | The local file path for sending files or documents. |
| photoCaption | Caption text for photos being sent. |
| fileCaption | Caption text for files being sent. |
| self_destruct_time | Time in seconds after which the message will self-destruct, if set. |
| sendAsVoice | Boolean flag indicating whether to send audio as a voice message. |
| audioSource | Source of the audio to send, either from binary data or file path. |
Output
JSON
chat_id- The ID of the chat where the message was sent.message_id- The ID of the sent message.success- Indicates if the message sending operation was successful.error- Error message if the sending operation failed.result- Detailed result object returned from the Telegram API after sending the message.
Dependencies
- TelePilot API credentials (apiId, apiHash, phoneNumber)
Troubleshooting
- Ensure the Telegram account is logged in before sending messages; otherwise, the node will throw a login error.
- Check file paths for media messages to confirm files exist and are accessible; missing files cause errors.
- For voice messages, use .ogg format to avoid compatibility issues and keep file size under 20MB.
- If the Telegram API returns errors like 'CHAT_WRITE_FORBIDDEN', verify the bot or user has permission to send messages in the chat.
- Use the /help command in the ChatTrigger node for login assistance and troubleshooting guidance.
Links
- TelePilot Login Guide - Instructions for logging in and authenticating the Telegram account for TelePilot.