Actions27
- Chat Actions
- File Actions
- Group Actions
- Message Actions
- User Actions
Overview
The node "Telegram CoPilot" provides an interface to interact with Telegram via the TelePilot API. It supports a wide range of Telegram operations such as managing chats, messages, users, groups, contacts, and files. Specifically, the Join Chat operation allows the user to join a Telegram chat by providing the chat's unique ID.
This node is beneficial for automating Telegram workflows, such as joining group chats automatically, sending messages, retrieving chat history, or managing chat members. For example, you could use it to programmatically join a chat when triggered by an event in another system, enabling further automated interactions within that chat.
Properties
Name | Meaning |
---|---|
Chat ID | The unique identifier of the Telegram chat to join. This is a required string property. |
Output
The output is a JSON array containing the result of the invoked Telegram API method corresponding to the join chat action. The structure typically includes details about the chat joined, such as chat metadata returned by the Telegram API.
No binary data output is indicated for this operation.
Example output (simplified):
[
{
"_": "chat",
"id": 123456789,
"title": "Example Chat",
"type": "group",
...
}
]
Dependencies
- Requires an active Telegram API credential configured in n8n, including API ID, API hash, and phone number.
- Depends on the TelePilot Node Connection Manager to handle client sessions and authentication.
- Requires the user to be logged in via the login process before performing chat operations.
- Network access to Telegram servers is necessary.
Troubleshooting
- Not logged in / Unauthorized errors: If the session is closed or unauthorized, the node will throw an error prompting to log in again. Use the login flow provided by the node (e.g., via the
/start
command) to authenticate. - Invalid Chat ID: Providing an incorrect or non-existent chat ID may cause the operation to fail or return an error from Telegram.
- Session closed errors: If the client session was closed unexpectedly, the node marks the client as closed and requires re-login.
- Command input issues: When using commands in login mode, unsupported commands will prompt help instructions.
- Ensure the Telegram account used has permission to join the specified chat.
Links and References
- TelePilot Login Guide
- Telegram Bot API Documentation (for general understanding of chat concepts)
- TelePilot Official Website