User → Get Me
AI-generatedOverview
This node integrates with Telegram using the GramJS library to perform various actions related to Telegram users, messages, and chats. Specifically for the User resource with the Get Me operation, it retrieves information about the currently authenticated Telegram user.
Common scenarios where this node is beneficial include:
- Automatically fetching the current user's Telegram profile details for logging or verification.
- Using the current user info as part of a workflow that interacts with Telegram chats or messages.
- Debugging or confirming the identity of the Telegram session in use.
Example: A workflow might start by retrieving the current user's info to confirm the bot or account identity before sending messages or managing chats.
Properties
| Name | Meaning |
|---|---|
| Additional Options | Collection of optional settings: - Parse Mode: How to parse message text (None, Markdown, HTML) - Silent: Whether to send messages silently (boolean) |
Note: For the Get Me operation on the User resource, the "Additional Options" property is available but not used in this operation's logic.
Output
The output JSON contains the Telegram user object representing the current authenticated user. This includes typical user fields such as username, first name, last name, user ID, and other profile details as returned by the Telegram API via GramJS.
Output example structure (simplified):
{
"id": 123456789,
"firstName": "John",
"lastName": "Doe",
"username": "johndoe",
"phone": "+1234567890",
...
}
No binary data is output for this operation.
Dependencies
- Requires an API authentication credential for Telegram (API ID, API Hash, and a session string).
- Uses the GramJS Telegram client library to interact with Telegram.
- The node expects a valid Telegram session string for authentication; phone code or password authentication is not supported within the node.
- No additional environment variables are required beyond the configured credentials.
Troubleshooting
- Authentication errors: If the session string is invalid or expired, the node will throw an authentication error. To resolve, generate a new session string externally and update the credentials.
- Unsupported authentication methods: The node does not support phone code or password authentication flows. Users must provide a valid session string.
- Unknown errors: Any unexpected errors during execution will be reported with their message. Check network connectivity and credential validity.
- Empty or malformed output: Ensure the Telegram API credentials are correct and the session is active.