Actions26
- Chat Actions
- File Actions
- Group Actions
- Message Actions
- User Actions
Overview
The node "Telegram CoPilot" integrates with the Telegram API to perform various chat-related operations. Specifically, the Join Chat operation allows a user to join a Telegram chat by providing the chat's unique ID. This is useful in scenarios where automation workflows need to programmatically join group chats or channels to monitor messages, participate in discussions, or manage chat memberships.
Practical examples include:
- Automatically joining a new project group chat when a user subscribes to a service.
- Joining public Telegram channels to scrape or analyze content.
- Integrating Telegram chat membership management into broader automation pipelines.
Properties
| Name | Meaning |
|---|---|
| Chat ID | The unique identifier of the Telegram chat to join. This must be provided as a string representing the chat's ID. |
Output
The node outputs an array of JSON objects representing the result of the join chat operation. The exact structure depends on the Telegram API response but typically includes details about the chat joined, such as chat metadata and status confirmation.
No binary data output is indicated for this operation.
Dependencies
- Requires an active Telegram API authentication credential (an API key and associated login).
- Depends on the
TelePilotNodeConnectionManagerto manage Telegram client sessions. - Requires prior successful login via phone number authentication using the node’s login mechanism.
- The node uses the Telegram TDLib API under the hood, so proper session management and authentication are essential.
Troubleshooting
- Session Not Logged In: If the Telegram account is not logged in, the node will throw an error prompting the user to log in first. Use the login operation with phone number authentication before attempting to join a chat.
- Closed Client Error: If the client session was closed or terminated, the node suggests re-login to restore the session.
- Unauthorized Errors: These indicate invalid or expired credentials; re-authentication is required.
- Invalid Chat ID: Providing an incorrect or non-existent chat ID may cause the operation to fail silently or return an error from Telegram.
- Network Issues: Connectivity problems can prevent the node from communicating with Telegram servers.
Links and References
- Telegram TDLib Documentation
- Telepilot Login Guide (for setting up authentication)
- Telegram Bot API Overview (general Telegram API reference)