Actions30
- Chat Actions
- Custom Request Actions
- File Actions
- Group Actions
- Message Actions
- User Actions
Overview
This node integrates with the Telegram API via the TelePilot library to perform various Telegram-related actions. Specifically, for the User resource and the Get User Full Info operation, it retrieves comprehensive information about a specified Telegram user by their user ID.
Common scenarios where this node is beneficial include:
- Fetching detailed profile data of a Telegram user for analytics or CRM integration.
- Automating user data retrieval in chatbots or Telegram management workflows.
- Enriching user records in external systems with Telegram user details.
Example use case: Given a Telegram user ID, the node fetches full user info such as profile photos, status, and other metadata, which can then be used downstream in an automation workflow.
Properties
| Name | Meaning |
|---|---|
| User ID | The unique identifier of the Telegram user whose full information you want to retrieve. |
Output
The node outputs an array of JSON objects representing the response from the Telegram API for the requested user. For the Get User Full Info operation, the output JSON contains detailed user information including but not limited to:
- Basic user profile data (e.g., first name, last name, username).
- Profile photos.
- Status information.
- Additional metadata related to the user's Telegram account.
The exact structure follows Telegram's API schema for "userFullInfo" objects.
No binary data output is produced by this operation.
Dependencies
- Requires an active Telegram API authentication credential (an API key and associated login session).
- Depends on the TelePilot library and its connection manager to handle Telegram client sessions.
- The node expects that the Telegram account is logged in and authorized; otherwise, it will prompt for login or throw an error.
- No additional environment variables are explicitly required beyond the Telegram API credentials configured in n8n.
Troubleshooting
- Error: "Please login" — This indicates the Telegram session is not authenticated. Resolve by performing the login process using the appropriate login operation or node.
- Session closed or terminated errors — The Telegram client session may have expired or been closed. Re-login is necessary.
- Unauthorized errors — The provided credentials are invalid or expired. Refresh or re-enter the Telegram API credentials.
- If the user ID is invalid or does not exist, the Telegram API may return an error or empty result.
- Network connectivity issues can cause invocation failures; ensure stable internet access.
- When encountering unexpected errors, enabling debug logs (the node uses debug logging internally) may help diagnose issues.
Links and References
- Telegram API Documentation - Users
- TelePilot Official Site
- TelePilot Login Guide (for resolving authentication issues)