Actions33
- Chat Actions
- Custom Request Actions
- File Actions
- Group Actions
- Message Actions
- User Actions
Overview
The node "Telegram CoPilot" integrates with the Telegram API to perform a wide range of Telegram-related actions programmatically. Specifically, for the Chat resource and Join Chat operation, it allows the user to join a Telegram chat by providing the chat's unique identifier. This is useful in scenarios where automated workflows need to interact with group chats or channels, such as joining a chat before sending messages, retrieving chat history, or managing chat members.
Practical examples include:
- Automatically joining a Telegram group when triggered by an external event.
- Joining a chat to monitor messages or perform administrative tasks.
- Integrating Telegram chat membership management into broader automation pipelines.
Properties
| Name | Meaning |
|---|---|
| Chat ID | The unique identifier of the Telegram chat to join. Required to specify which chat to join. |
Output
The output of the node is a JSON array containing the response from the Telegram API after attempting to join the specified chat. The structure typically includes details about the chat joined, such as its ID, type, title, and other metadata returned by the Telegram API.
No binary data output is produced by this operation.
Example output snippet (conceptual):
{
"id": 123456789,
"type": "group",
"title": "Example Group Chat",
"status": "joined"
}
Dependencies
- Requires an active Telegram API authentication credential (an API key credential) configured in n8n.
- Depends on the TelePilotNodeConnectionManager internal service to manage Telegram client sessions.
- The node expects the Telegram account to be logged in and authorized; otherwise, it will prompt for login via a companion ChatTrigger node or manual login steps.
- No additional external dependencies beyond the Telegram API and the provided credentials.
Troubleshooting
Common issues:
- Attempting to join a chat without being logged in will result in an error prompting the user to log in first.
- Invalid or incorrect Chat ID may cause the Telegram API to reject the request.
- Network or API rate limits could cause temporary failures.
Error messages and resolutions:
"Please login: https://telepilot.co/login-howto": Indicates the Telegram session is not authenticated. Resolve by performing login using the ChatTrigger node or following the linked guide."Session was closed or terminated. Please login again": The stored session has expired or been closed. Re-login is required."Unauthorized": Credentials are invalid or expired. Re-authenticate your Telegram API credentials.- Errors related to invalid chat IDs or permissions usually indicate that the bot/user does not have access to the target chat.
Links and References
- TelePilot Login Guide — Instructions for logging in and managing Telegram sessions.
- Telegram Bot API Documentation — Official Telegram API reference.
- n8n Documentation — General information on creating and using custom nodes in n8n.