Actions33
- Chat Actions
- Custom Request Actions
- File Actions
- Group Actions
- Message Actions
- User Actions
Overview
This node acts as a personal Telegram assistant, enabling interaction with the Telegram API to manage chats, messages, users, and files. It supports a wide range of Telegram operations such as opening chats, sending messages (text, photo, video, audio, files), editing or deleting messages, joining chats, and retrieving chat history.
The "Open Chat" operation specifically opens a chat by its ID, which can be useful for preparing a chat session before sending messages or performing other chat-related actions.
Practical examples:
- Automatically open a specific chat to prepare for sending scheduled messages.
- Open a chat to fetch recent messages or perform moderation tasks.
- Use in workflows that require interacting with a particular chat context dynamically.
Properties
| Name | Meaning |
|---|---|
| Chat ID | The unique identifier of the chat to open. This is required to specify which chat to open. |
Output
The output is an array of JSON objects representing the result of the invoked Telegram API method corresponding to the "openChat" operation. Typically, this includes details about the opened chat such as its metadata and status.
If errors occur, the output may contain error information within the JSON structure.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Telegram API.
- Depends on the TelePilotNodeConnectionManager service to manage Telegram client sessions and invoke API calls.
- The node expects a valid logged-in Telegram session; otherwise, it prompts for login via phone number and authentication code.
- Uses environment configurations related to Telegram API credentials (API ID, API hash, phone number).
Troubleshooting
- Not logged in error: If the Telegram account is not logged in, the node will throw an error instructing to use the login flow first. Use the ChatTrigger node with the login operation to authenticate.
- Session closed or terminated: If the client session is closed unexpectedly, the node suggests re-login.
- Invalid Chat ID: Providing an incorrect or non-existent chat ID may cause the API call to fail.
- Permission issues: Attempting to open chats where the user lacks permission may result in errors.
- Network or API errors: General Telegram API errors are returned with messages; ensure network connectivity and valid credentials.
Links and References
- Telepilot Login Guide — Instructions for logging in and managing Telegram sessions.
- Telegram Bot API Documentation — Official Telegram API reference (note: TelePilot uses TDLib, but this is useful for general understanding).