Actions26
- 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 Chats (Search in Username, Title) operation, it allows users to search for public Telegram chats by querying their usernames and titles.
Common scenarios where this node is beneficial include:
- Finding public Telegram groups or channels related to a specific topic or keyword.
- Automating discovery of relevant public chats for marketing, community engagement, or research purposes.
- Integrating Telegram chat search into larger workflows that require dynamic retrieval of chat information.
For example, a user could input a query like "technology news" to find public Telegram chats whose usernames or titles contain those keywords.
Properties
| Name | Meaning |
|---|---|
| Query | Text string used to search public chats by looking in their username and title. This is required. |
Output
The output is a JSON array containing the results of the public chat search. Each element in the array represents a public chat matching the query criteria, including details such as chat identifiers, usernames, titles, and other metadata returned by the Telegram API.
No binary data output is indicated for this operation.
Dependencies
- Requires an active Telegram API authentication credential (an API key credential) configured in n8n.
- Depends on the internal
TelePilotNodeConnectionManagerto manage Telegram client sessions. - The node requires a logged-in Telegram session; otherwise, it prompts the user to log in using the login flow provided by the node.
- Network access to Telegram's API endpoints is necessary.
Troubleshooting
- Session Not Logged In: If the Telegram session is not logged in or has expired, the node will throw errors prompting re-login. Users should follow the login instructions 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 logging in again.
- Empty or Invalid Query: Since the query property is required, providing an empty string may result in no results or errors.
- Rate Limits or API Restrictions: Excessive requests might be throttled by Telegram; handle accordingly.