Actions27
- Chat Actions
- File Actions
- Group Actions
- Message Actions
- User Actions
Overview
This node, named "Telegram CoPilot," integrates with the Telegram API to perform various Telegram-related actions programmatically. Specifically, for the Chat resource and the Search Public Chat (by Username) operation, it allows users to search for a public Telegram chat by providing its username.
Common scenarios where this node is beneficial include:
- Automating the retrieval of public chat information based on known usernames.
- Integrating Telegram chat searches into workflows that require dynamic chat lookups.
- Building bots or automation tools that need to interact with public Telegram chats without manual searching.
For example, a user can input a Telegram chat username, and the node will return detailed information about that public chat, which can then be used in subsequent workflow steps such as sending messages or joining the chat.
Properties
| Name | Meaning |
|---|---|
| Chat Username | The username of the public Telegram chat to search for. This must be provided as a string. |
Output
The node outputs an array of JSON objects representing the result of the invoked Telegram API method searchPublicChat. The structure typically includes details about the public chat found by the username, such as chat ID, title, type, and other metadata returned by Telegram's API.
If the node supports binary data output (not explicitly shown for this operation), it would represent files or media related to chats, but for this operation, the output is purely JSON-based chat information.
Dependencies
- Requires an API key credential for Telegram (referred generically as "an API key credential").
- Depends on the internal TelePilot client connection manager to handle Telegram sessions and API calls.
- Requires proper login/authentication via the Telegram API before performing operations.
- The node uses the Telegram TDLib-based client internally to invoke Telegram API methods.
Troubleshooting
- Session Not Logged In: If the Telegram session is not logged in or has expired, the node throws errors prompting the user to log in again using the login flow described at https://telepilot.co/login-howto.
- Unauthorized Errors: These indicate invalid or expired credentials; re-authentication is required.
- Closed Client Errors: If the client session was closed unexpectedly, the node suggests re-login.
- Invalid Username: If the username does not correspond to any public chat, the output may be empty or contain error information from Telegram.
- Ensure the username is correctly formatted and exists as a public chat on Telegram.
Links and References
- TelePilot Login Guide — Instructions for logging in and managing Telegram sessions.
- Telegram TDLib Documentation — For understanding the underlying Telegram API methods used.
- Telegram Bots FAQ — General info about Telegram bot interactions.
This summary focuses on the Chat resource and the Search Public Chat (by Username) operation as requested.