Actions27
- Chat Actions
- File Actions
- Group Actions
- Message Actions
- User Actions
Overview
The node acts as a personal Telegram assistant, enabling interaction with the Telegram API to perform various user-related operations. Specifically for the "User" resource and the "Get User" operation, it retrieves detailed information about a Telegram user by their user ID. This is useful in scenarios where you need to fetch user profile data, verify user existence, or gather user details for further processing within an automation workflow.
Practical examples include:
- Fetching user details to personalize messages.
- Verifying user identity before performing actions.
- Integrating Telegram user data into CRM or support systems.
Properties
| Name | Meaning |
|---|---|
| User ID | The unique identifier of the Telegram user whose information you want to retrieve. Example: "122323". |
Output
The output is a JSON array containing the user information object returned from the Telegram API. This object includes all available details about the specified user, such as username, first name, last name, status, and other profile-related fields as provided by Telegram.
No binary data output is involved in this operation.
Dependencies
- Requires an active Telegram API authentication credential (an API key credential) configured in n8n.
- Depends on the TelePilotNodeConnectionManager to manage Telegram client sessions.
- The node requires the Telegram account to be logged in; otherwise, it will prompt for login via a linked ChatTrigger node.
- Network access to Telegram's API endpoints is necessary.
Troubleshooting
Common issues:
- "Session was closed or terminated": Indicates that the Telegram session has expired or been disconnected. Solution: Re-login using the ChatTrigger node and follow the login instructions.
- "Unauthorized": The Telegram API credentials are invalid or the session is not authenticated. Solution: Re-authenticate by logging in again.
- Missing or incorrect User ID parameter: Ensure the User ID is provided and correctly formatted.
Error handling:
- The node throws errors if the Telegram client session is closed or unauthorized, guiding users to re-login.
- If the user ID does not exist or is invalid, the Telegram API may return an error which will propagate through the node.
Links and References
- Telegram API documentation: https://core.telegram.org/api
- TelePilot login guide: https://telepilot.co/login-howto