Actions56
- 袙褏芯写 Actions
- 袚褉褍锌锌邪 Actions
- 袣芯薪褌邪泻褌 Actions
- 袩芯写邪褉芯泻 Actions
- 袩芯谢褜蟹芯胁邪褌械谢褜 Actions
- 袩芯谢褜蟹芯胁邪褌械谢褜褋泻懈泄 蟹邪锌褉芯褋 Actions
- 小芯芯斜褖械薪懈械 Actions
- 肖邪泄谢 Actions
- 效邪褌 Actions
- 袩芯谢褍褔懈褌褜 褋锌懈褋芯泻 锌邪锌芯泻
- 袪械写邪泻褌懈褉芯胁邪褌褜 锌邪锌泻褍
- 袛芯斜邪胁懈褌褜 褔邪褌 胁 锌邪锌泻褍
- 校写邪谢懈褌褜 褔邪褌 懈蟹 锌邪锌泻懈
- 袛芯斜邪胁懈褌褜 褍褔邪褋褌薪懈泻芯胁 胁 褔邪褌
- 袟邪泻褉褘褌褜 褔邪褌
- 袨褌泻褉褘褌褜 褔邪褌
- 袨褌屑械褌懈褌褜 褔邪褌 泻邪泻 薪械锌褉芯褔懈褌邪薪薪褘泄
- 袨褌锌褉邪胁懈褌褜 写械泄褋褌胁懈械 褔邪褌邪
- 袩芯懈褋泻 锌褍斜谢懈褔薪芯谐芯 褔邪褌邪 (锌芯 懈屑械薪懈 锌芯谢褜蟹芯胁邪褌械谢褟)
- 小芯蟹写邪褌褜 斜懈蟹薪械褋-褋褋褘谢泻褍 褔邪褌邪
- 校写邪谢懈褌褜 斜懈蟹薪械褋-褋褋褘谢泻褍 褔邪褌邪
- 袩芯懈褋泻 锌褍斜谢懈褔薪褘褏 褔邪褌芯胁 (袩芯懈褋泻 胁 懈屑械薪懈, 蟹邪谐芯谢芯胁泻械)
- 袩芯谢褍褔懈褌褜 懈薪褎芯褉屑邪褑懈褞 芯 褋褋褘谢泻械 锌褉懈谐谢邪褕械薪懈褟 胁 褔邪褌
- 袩芯谢褍褔懈褌褜 懈褋褌芯褉懈褞 褔邪褌邪
- 袩芯谢褍褔懈褌褜 锌谢邪褌薪褘械 锌芯褋褌褘 懈蟹 褔邪褌邪
- 袩芯谢褍褔懈褌褜 褍褔邪褋褌薪懈泻芯胁 褔邪褌邪, 锌褉懈褋芯械写懈薪懈胁褕懈褏褋褟 锌芯 褋褋褘谢泻械 锌褉懈谐谢邪褕械薪懈褟
- 袩芯谢褍褔懈褌褜 懈薪褎芯褉屑邪褑懈褞 芯 褔邪褌械
- 袩芯谢褍褔懈褌褜 褔邪褌褘
- 袩褉懈褋芯械写懈薪懈褌褜褋褟 泻 褔邪褌褍
- 小芯蟹写邪褌褜 褋褍锌械褉谐褉褍锌锌褍 懈谢懈 泻邪薪邪谢
- 校写邪谢懈褌褜 褔邪褌
- 袩芯谢褍褔懈褌褜 褋锌懈褋芯泻 斜懈蟹薪械褋-褋褋褘谢芯泻
- 袟胁械蟹写褘 Actions
- 袠褋褌芯褉懈懈 Actions
袩芯谢褜蟹芯胁邪褌械谢褜 → 袩芯谢褍褔懈褌褜 懈薪褎芯褉屑邪褑懈褞 芯 褋械斜械
AI-generatedOverview
This node interacts with the Telegram CoPilot API to perform login operations using a phone number. It supports commands to start login, stop the session, clear local session data, and provide help or status information. The node manages authentication states including waiting for phone number, authentication code, and multi-factor authentication password. It is useful for automating Telegram login workflows and managing session states programmatically.
Use Case Examples
- Automate Telegram login by sending commands like /start and /stop through the node.
- Use the node to handle multi-factor authentication during Telegram login.
- Clear local session data to reset login state and start fresh authentication.
Properties
| Name | Meaning |
|---|---|
| resource | The resource to operate on, here it is Telegram login. |
| operation | The specific login operation to perform. |
Output
JSON
text- Text messages or status updates related to login commands and states.message- Error or informational messages returned during login operations.error- Error details if any error occurs during login.success- Boolean indicating success of certain operations like sending video notes.result- Result data from operations such as sending messages or login status.
Dependencies
- Requires Telegram API credentials including apiId, apiHash, and phoneNumber.
Troubleshooting
- Common errors include failure to initialize client due to incorrect credentials or network issues.
- Unauthorized errors indicate the need to login again using the login commands.
- Session closed errors require clearing local session data and re-authenticating.
- Ensure the phone number and authentication codes are correctly provided during login.
Links
- TelePilot Login Guide - Official guide for logging in with TelePilot node using phone number and authentication commands.