User → Get
AI-generatedOverview
This node interacts with Telegram users via the GramJS library, specifically allowing you to retrieve information about a Telegram user by their identifier. It supports fetching details using a user ID, username, or phone number.
Common scenarios where this node is useful include:
- Retrieving profile information of a specific Telegram user for automation workflows.
- Verifying user details before sending messages or performing other operations.
- Integrating Telegram user data into CRM or support systems.
For example, you can input a Telegram username and get back detailed user information such as their full name, user ID, and other metadata.
Properties
| Name | Meaning |
|---|---|
| User ID | The identifier of the user to fetch. Can be a user ID, username, or phone number. |
| Additional Options | Optional settings: |
| - Parse Mode | How to parse message text (None, Markdown, HTML). Not directly used in "Get User" but available for consistency. |
| - Silent | Whether to send messages silently. Not applicable for "Get User" operation but present in options. |
Output
The output is a JSON object containing the user information retrieved from Telegram. This includes all available user entity details such as user ID, username, first and last names, and other metadata provided by the Telegram API.
Example output structure (simplified):
{
"id": 123456789,
"username": "exampleuser",
"firstName": "John",
"lastName": "Doe",
"phone": "+1234567890",
...
}
No binary data output is produced for this operation.
Dependencies
- Requires an API authentication credential for Telegram (an API ID, API hash, and session string).
- Uses the GramJS Telegram client library to connect and interact with Telegram.
- The node expects a valid session string for authentication; phone code or password authentication is not supported within this node.
Troubleshooting
- Authentication errors: If the node throws an authentication error, ensure that the session string is valid and correctly configured. Phone code or password authentication is not supported, so these must be handled outside the node.
- User not found: If the specified user ID, username, or phone number does not exist or is invalid, the node may throw an error or return no data.
- API limits: Telegram API rate limits may cause temporary failures; retry after some time if encountering such issues.
- Missing required parameters: The "User ID" property is mandatory; omitting it will cause the node to fail.