Actions26
- Chat Actions
- File Actions
- Group Actions
- Message Actions
- User Actions
Overview
This node, named "Telegram CoPilot," integrates with the Telegram platform to perform various operations on Telegram resources such as users, contacts, chats, messages, files, and groups. Specifically for the Chat resource and the Search Public Chats (Search in Username, Title) operation, it allows searching public Telegram chats by querying their usernames and titles.
Common scenarios where this node is beneficial include:
- Finding public Telegram channels or groups related to a specific topic by searching keywords in their username or title.
- Automating discovery of relevant public chats for marketing, community engagement, or information gathering.
- Integrating Telegram chat search into workflows that require dynamic retrieval of chat information based on user input or external triggers.
Practical example:
- A workflow that takes a keyword from a user input, uses this node to search public Telegram chats matching that keyword, and then processes or displays the found chats for further actions like joining or messaging.
Properties
| Name | Meaning |
|---|---|
| Query | The text string used to search public chats by looking in their username and title. Required. |
Output
The node outputs an array of JSON objects representing the search results of public Telegram chats matching the query. Each object contains detailed information about a public chat, including metadata such as chat ID, username, title, and other Telegram-specific chat properties.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating with the Telegram API via the TelePilot service.
- The node depends on the TelePilotNodeConnectionManager class to manage Telegram client sessions and invoke Telegram API methods.
- Proper login/authentication must be established before performing chat operations; otherwise, the node will throw errors prompting re-login.
- Network access to Telegram servers is required.
Troubleshooting
- Session Not Logged In: If the Telegram account session is not logged in or has expired, the node throws errors instructing to log in again using the ChatTrigger node and following the login guide at https://telepilot.co/login-howto.
- Unauthorized Errors: These indicate invalid or expired credentials; re-authentication is necessary.
- Closed Client Errors: Occur if the client session was closed unexpectedly; the node marks the client as closed and requires a new login.
- Empty or Invalid Query: Since the
queryproperty is required, providing an empty string may result in no results or errors. - Rate Limits or API Restrictions: As with any Telegram API usage, hitting rate limits or restrictions may cause failures; handle these gracefully in workflows.
Links and References
- TelePilot Login Guide — Instructions for logging in and managing Telegram sessions.
- Telegram API Documentation — Official Telegram API reference.
- TelePilot GitHub Repository (if publicly available) — For source code and issues.
This summary focuses on the Chat resource and the Search Public Chats operation as requested, based solely on static analysis of the provided source code and property definitions.