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, enabling automation and interaction with Telegram user accounts and chats. It supports a wide range of Telegram operations such as retrieving user information, managing chats, sending messages (text, audio, video, files, photos), and handling login sessions.
For the User - Get User operation specifically, the node fetches detailed information about a Telegram user by their user ID. This is useful in scenarios where you want to retrieve profile details or metadata about a specific Telegram user programmatically.
Practical examples:
- Fetching user details to display in a dashboard.
- Automating user data retrieval for customer support bots.
- Integrating Telegram user info into CRM or other backend systems.
Properties
| Name | Meaning |
|---|---|
| User ID | The unique identifier of the Telegram user whose information you want to retrieve. |
Output
The output is an array of JSON objects representing the response from the Telegram API for the requested user. For the "Get User" operation, the JSON contains detailed user information such as username, first name, last name, status, profile photos, and other metadata as provided by Telegram.
Example structure (simplified):
{
"id": 123456789,
"first_name": "John",
"last_name": "Doe",
"username": "johndoe",
"status": { /* user status info */ },
"profile_photo": { /* photo info */ },
...
}
If the node encounters errors (e.g., invalid user ID, unauthorized access), it may return error details within the JSON output.
Dependencies
- Requires an active Telegram API authentication credential (an API key credential with apiId, apiHash, and phoneNumber).
- Depends on the TelePilot library and its connection manager to handle Telegram client sessions.
- Node configuration must include valid Telegram credentials and proper session management.
- The node uses asynchronous calls to Telegram's TDLib via TelePilot.
Troubleshooting
Common issues:
- Not logged in or session expired: The node requires a valid Telegram session. If not logged in, it will throw an error prompting to log in using the login flow.
- Invalid User ID: Providing a non-existent or malformed user ID will result in an error or empty response.
- Network or API errors: Temporary connectivity issues or Telegram API restrictions can cause failures.
Error messages and resolutions:
"Please login: https://telepilot.co/login-howto": Indicates no active Telegram session. Resolve by performing the login operation with the ChatTrigger node as per the guide."A closed client cannot be reused, create a new Client": Session was closed unexpectedly; re-login required."Unauthorized": Credentials are invalid or expired; re-authenticate.- Other Telegram API errors are passed through; check the message for specifics.
To handle errors gracefully, enable "Continue On Fail" in the node settings to receive error details in the output instead of stopping execution.