Telegram CoPilot icon

Telegram CoPilot

袙邪褕 锌械褉褋芯薪邪谢褜薪褘泄 Telegram CoPilot

Actions56

袙褏芯写 → 袟邪泻褉褘褌褜 褋械褋褋懈褞

AI-generated

Overview

This node integrates with Telegram via the TelePilot API, enabling users to perform various Telegram-related operations programmatically. Specifically, for the resource 'user' and operation 'login with phone number', it facilitates the login process to a Telegram account using phone number authentication, including handling multi-factor authentication (MFA) and session management. This is useful for automating Telegram account login workflows, managing sessions, and interacting with Telegram's API securely within automation workflows.

Use Case Examples

  1. Automate Telegram login for a bot or service using phone number and MFA.
  2. Manage Telegram sessions programmatically to maintain persistent connections.
  3. Trigger Telegram actions post-login, such as sending messages or retrieving user info.

Output

JSON

  • message - General message or status information returned by the node
  • error - Error details if an error occurs during execution
  • new_transaction - Details of a new star transaction detected (for star transactions trigger)
  • timestamp - Timestamp of the event or transaction
  • transaction_details
    • id - ID of the star transaction
    • date - Date of the star transaction
    • amount - Amount involved in the star transaction
    • type - Type of the star transaction
    • status - Status of the star transaction
  • success - Indicates if an operation like sending a message was successful
  • result - Result data from operations such as sending messages or retrieving info
  • errorDetails
    • message - Detailed error message from Telegram API or internal errors
  • errorType - Categorized type of error for better handling

Dependencies

  • TelePilot API credentials (apiId, apiHash, phoneNumber)

Troubleshooting

  • Common issues include failure to initialize the Telegram client due to incorrect credentials or network issues.
  • Errors related to unauthorized access indicate the need to login again using the provided login flow.
  • File-related errors when sending media indicate missing or inaccessible files; ensure file paths are correct and files exist.
  • Errors mentioning 'CHAT_NOT_FOUND' or 'USER_NOT_FOUND' indicate invalid chat or user IDs; verify IDs before use.
  • For MFA, ensure the correct authentication code or password is provided when prompted.
  • If the session is closed or terminated, re-login is required as indicated by specific error messages.

Links

Discussion