Actions56
- 袙褏芯写 Actions
- 袚褉褍锌锌邪 Actions
- 袣芯薪褌邪泻褌 Actions
- 袩芯写邪褉芯泻 Actions
- 袩芯谢褜蟹芯胁邪褌械谢褜 Actions
- 袩芯谢褜蟹芯胁邪褌械谢褜褋泻懈泄 蟹邪锌褉芯褋 Actions
- 小芯芯斜褖械薪懈械 Actions
- 肖邪泄谢 Actions
- 效邪褌 Actions
- 袩芯谢褍褔懈褌褜 褋锌懈褋芯泻 锌邪锌芯泻
- 袪械写邪泻褌懈褉芯胁邪褌褜 锌邪锌泻褍
- 袛芯斜邪胁懈褌褜 褔邪褌 胁 锌邪锌泻褍
- 校写邪谢懈褌褜 褔邪褌 懈蟹 锌邪锌泻懈
- 袛芯斜邪胁懈褌褜 褍褔邪褋褌薪懈泻芯胁 胁 褔邪褌
- 袟邪泻褉褘褌褜 褔邪褌
- 袨褌泻褉褘褌褜 褔邪褌
- 袨褌屑械褌懈褌褜 褔邪褌 泻邪泻 薪械锌褉芯褔懈褌邪薪薪褘泄
- 袨褌锌褉邪胁懈褌褜 写械泄褋褌胁懈械 褔邪褌邪
- 袩芯懈褋泻 锌褍斜谢懈褔薪芯谐芯 褔邪褌邪 (锌芯 懈屑械薪懈 锌芯谢褜蟹芯胁邪褌械谢褟)
- 小芯蟹写邪褌褜 斜懈蟹薪械褋-褋褋褘谢泻褍 褔邪褌邪
- 校写邪谢懈褌褜 斜懈蟹薪械褋-褋褋褘谢泻褍 褔邪褌邪
- 袩芯懈褋泻 锌褍斜谢懈褔薪褘褏 褔邪褌芯胁 (袩芯懈褋泻 胁 懈屑械薪懈, 蟹邪谐芯谢芯胁泻械)
- 袩芯谢褍褔懈褌褜 懈薪褎芯褉屑邪褑懈褞 芯 褋褋褘谢泻械 锌褉懈谐谢邪褕械薪懈褟 胁 褔邪褌
- 袩芯谢褍褔懈褌褜 懈褋褌芯褉懈褞 褔邪褌邪
- 袩芯谢褍褔懈褌褜 锌谢邪褌薪褘械 锌芯褋褌褘 懈蟹 褔邪褌邪
- 袩芯谢褍褔懈褌褜 褍褔邪褋褌薪懈泻芯胁 褔邪褌邪, 锌褉懈褋芯械写懈薪懈胁褕懈褏褋褟 锌芯 褋褋褘谢泻械 锌褉懈谐谢邪褕械薪懈褟
- 袩芯谢褍褔懈褌褜 懈薪褎芯褉屑邪褑懈褞 芯 褔邪褌械
- 袩芯谢褍褔懈褌褜 褔邪褌褘
- 袩褉懈褋芯械写懈薪懈褌褜褋褟 泻 褔邪褌褍
- 小芯蟹写邪褌褜 褋褍锌械褉谐褉褍锌锌褍 懈谢懈 泻邪薪邪谢
- 校写邪谢懈褌褜 褔邪褌
- 袩芯谢褍褔懈褌褜 褋锌懈褋芯泻 斜懈蟹薪械褋-褋褋褘谢芯泻
- 袟胁械蟹写褘 Actions
- 袠褋褌芯褉懈懈 Actions
袙褏芯写 → 校写邪谢懈褌褜 Td_database
AI-generatedOverview
This node integrates with Telegram via the TelePilot API, enabling various Telegram operations such as user management, chat handling, message sending, and session management. It supports login via phone number, managing chat folders, sending different types of messages (text, audio, video, photo, files), handling chat members, and retrieving chat or user information. The node is useful for automating Telegram interactions, managing Telegram accounts, and processing Telegram data programmatically within workflows.
Use Case Examples
- Automate sending messages or media to Telegram chats.
- Manage Telegram chat folders and memberships.
- Retrieve user or chat information for analytics or monitoring.
- Implement Telegram login and session management within workflows.
Properties
| Name | Meaning |
|---|---|
| resource | The Telegram resource to operate on, e.g., user, chat, message, group, etc. |
| operation | The specific operation to perform on the selected resource, e.g., getMe, sendMessage, getChatHistory, etc. |
Output
JSON
json- The JSON response from the TelePilot API for the requested operation, containing data such as user info, chat details, messages, or operation results.
Dependencies
- TelePilot API credentials (apiId, apiHash, phoneNumber) are required for authentication and API access.
Troubleshooting
- Common errors include client initialization failures, unauthorized access, and session closure. Users should ensure valid credentials and active sessions.
- Errors related to chat or user not found indicate invalid IDs or permissions; verify input parameters.
- File-related errors when sending media indicate missing or inaccessible files; ensure correct file paths and existence.
- API errors like 'CHAT_WRITE_FORBIDDEN' or 'FILE_REFERENCE_EXPIRED' require checking user permissions or retrying with valid references.
Links
- TelePilot Login Guide - Instructions for logging in and managing Telegram sessions with TelePilot.