Actions56
- 袙褏芯写 Actions
- 袚褉褍锌锌邪 Actions
- 袣芯薪褌邪泻褌 Actions
- 袩芯写邪褉芯泻 Actions
- 袩芯谢褜蟹芯胁邪褌械谢褜 Actions
- 袩芯谢褜蟹芯胁邪褌械谢褜褋泻懈泄 蟹邪锌褉芯褋 Actions
- 小芯芯斜褖械薪懈械 Actions
- 肖邪泄谢 Actions
- 效邪褌 Actions
- 袩芯谢褍褔懈褌褜 褋锌懈褋芯泻 锌邪锌芯泻
- 袪械写邪泻褌懈褉芯胁邪褌褜 锌邪锌泻褍
- 袛芯斜邪胁懈褌褜 褔邪褌 胁 锌邪锌泻褍
- 校写邪谢懈褌褜 褔邪褌 懈蟹 锌邪锌泻懈
- 袛芯斜邪胁懈褌褜 褍褔邪褋褌薪懈泻芯胁 胁 褔邪褌
- 袟邪泻褉褘褌褜 褔邪褌
- 袨褌泻褉褘褌褜 褔邪褌
- 袨褌屑械褌懈褌褜 褔邪褌 泻邪泻 薪械锌褉芯褔懈褌邪薪薪褘泄
- 袨褌锌褉邪胁懈褌褜 写械泄褋褌胁懈械 褔邪褌邪
- 袩芯懈褋泻 锌褍斜谢懈褔薪芯谐芯 褔邪褌邪 (锌芯 懈屑械薪懈 锌芯谢褜蟹芯胁邪褌械谢褟)
- 小芯蟹写邪褌褜 斜懈蟹薪械褋-褋褋褘谢泻褍 褔邪褌邪
- 校写邪谢懈褌褜 斜懈蟹薪械褋-褋褋褘谢泻褍 褔邪褌邪
- 袩芯懈褋泻 锌褍斜谢懈褔薪褘褏 褔邪褌芯胁 (袩芯懈褋泻 胁 懈屑械薪懈, 蟹邪谐芯谢芯胁泻械)
- 袩芯谢褍褔懈褌褜 懈薪褎芯褉屑邪褑懈褞 芯 褋褋褘谢泻械 锌褉懈谐谢邪褕械薪懈褟 胁 褔邪褌
- 袩芯谢褍褔懈褌褜 懈褋褌芯褉懈褞 褔邪褌邪
- 袩芯谢褍褔懈褌褜 锌谢邪褌薪褘械 锌芯褋褌褘 懈蟹 褔邪褌邪
- 袩芯谢褍褔懈褌褜 褍褔邪褋褌薪懈泻芯胁 褔邪褌邪, 锌褉懈褋芯械写懈薪懈胁褕懈褏褋褟 锌芯 褋褋褘谢泻械 锌褉懈谐谢邪褕械薪懈褟
- 袩芯谢褍褔懈褌褜 懈薪褎芯褉屑邪褑懈褞 芯 褔邪褌械
- 袩芯谢褍褔懈褌褜 褔邪褌褘
- 袩褉懈褋芯械写懈薪懈褌褜褋褟 泻 褔邪褌褍
- 小芯蟹写邪褌褜 褋褍锌械褉谐褉褍锌锌褍 懈谢懈 泻邪薪邪谢
- 校写邪谢懈褌褜 褔邪褌
- 袩芯谢褍褔懈褌褜 褋锌懈褋芯泻 斜懈蟹薪械褋-褋褋褘谢芯泻
- 袟胁械蟹写褘 Actions
- 袠褋褌芯褉懈懈 Actions
效邪褌 → 袛芯斜邪胁懈褌褜 褍褔邪褋褌薪懈泻芯胁 胁 褔邪褌
AI-generatedOverview
This node interacts with Telegram chats to perform various chat-related operations such as retrieving chat history, sending messages (text, photo, video, audio, file), managing chat members, editing chat folders, handling chat invite links, and more. It is useful for automating Telegram chat management and messaging tasks within workflows, for example, sending automated messages to a chat, retrieving chat history for analysis, or managing chat members programmatically.
Use Case Examples
- Automatically send a text message to a Telegram chat when a specific event occurs.
- Retrieve the chat history of a Telegram group for logging or analysis.
- Add multiple users to a Telegram supergroup or channel automatically.
- Edit chat folder properties such as title, icon, and color via automation.
Properties
| Name | Meaning |
|---|---|
| Chat ID | The unique identifier of the Telegram chat to operate on. Required for most chat-related operations. |
| User IDs | Comma-separated list of user IDs to be added to a Supergroup or Channel. Used specifically for the addChatMembers operation. |
Output
JSON
chat_id- The ID of the chat involved in the operation.message_ids- IDs of messages involved in operations like delete or forward.result- Result object returned from Telegram API for the performed operation.success- Indicates if the operation was successful.error- Error message if the operation failed.new_transaction- Details of a new star transaction detected in trigger operations.timestamp- Timestamp of the operation or event.
Dependencies
- Telegram API accessed via TelePilot API credentials including apiId, apiHash, and phoneNumber for authentication.
Troubleshooting
- Ensure the Telegram account is logged in properly; otherwise, the node will throw login-related errors and suggest using the loginWithPhoneNumber action.
- Common errors include 'Client is not initialized' if the Telegram client session is not established, and 'Unauthorized' if credentials are invalid or session expired.
- Errors related to chat permissions such as 'CHAT_ADMIN_REQUIRED' indicate the user must have admin rights to perform certain actions.
- File-related errors when sending media (e.g., audio or video) may occur if the file path is invalid or the file size exceeds Telegram limits.
- Use the continueOnFail option to handle errors gracefully in workflows.
Links
- TelePilot Login Guide - Instructions on how to log in and authenticate the Telegram account for this node.
- Telegram Bot API Documentation - Official Telegram API documentation for understanding available chat and message operations.