Telegram CoPilot icon

Telegram CoPilot

Your Personal Telegram CoPilot

Actions27

Overview

This node integrates with Telegram via the TelePilot API, enabling automation and interaction with Telegram accounts. 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 communities for marketing, research, or engagement purposes.
  • Integrating Telegram chat search into broader workflows, such as notifying users about new relevant groups.

Example: A user wants to find all public Telegram chats related to "technology news". They provide the query string "technology news" to this node, which returns matching public chats with usernames or titles containing that phrase.

Properties

Name Meaning
Query The text string used to search public Telegram chats by looking in their username and title.

Output

The node outputs an array of JSON objects representing the public chats found matching the query. Each object contains details about a public chat, such as its username, title, and other metadata provided by the Telegram API.

If the node supports binary data output (not applicable specifically for this operation), it would typically represent files or media downloaded from Telegram.

Dependencies

  • Requires an active Telegram account authenticated via the TelePilot API.
  • Needs an API key credential for the TelePilot service configured in n8n.
  • The node depends on the TelePilotNodeConnectionManager to manage Telegram client sessions.
  • Users must be logged in through the login process supported by the node before performing chat operations.

Troubleshooting

  • Not logged in error: If the node throws errors indicating the session is closed or unauthorized, ensure you have completed the login process using the login operation with phone number authentication.
  • Empty results: If no public chats are returned, verify the query string is correct and that there are public chats matching the criteria.
  • API limits or connectivity issues: Network problems or API rate limits may cause failures; check your internet connection and API usage.
  • Session expired: If the session expires, re-login using the login commands described in the node's documentation.

Links and References

Discussion