Actions26
- Chat Actions
- File Actions
- Group Actions
- Message Actions
- User Actions
Overview
This node, named "Telegram CoPilot," provides extensive integration with the Telegram messaging platform via its API. It allows users to perform a wide range of Telegram operations such as managing chats, messages, users, groups, files, and contacts programmatically within n8n workflows.
The Get Messages operation under the Message resource specifically retrieves a single message from a specified chat by its message ID. This is useful for scenarios where you want to fetch details of a particular message, for example, to analyze its content, forward it, or use it as part of a larger automation workflow.
Practical examples:
- Fetching a specific message to extract text or metadata for logging or processing.
- Retrieving a message before editing or forwarding it.
- Using message data to trigger conditional logic in workflows.
Properties
| Name | Meaning |
|---|---|
| Chat ID | The unique identifier of the chat from which to retrieve the message. |
| Message ID | The unique identifier of the message to retrieve within the specified chat. |
These properties are required inputs for the Get Messages operation.
Output
The output is a JSON array containing the result of the invoked Telegram API call. For the Get Messages operation, the JSON object represents the detailed information about the requested message, including but not limited to:
- Message content (text, media, etc.)
- Sender information
- Timestamps
- Message status and metadata
If the node supports binary data outputs (e.g., for photos or files), it would be included accordingly, but for this operation, the focus is on JSON message data.
Dependencies
- Requires an active Telegram API authentication credential (an API key credential) configured in n8n.
- Depends on the TelePilot library and its connection manager to handle Telegram client sessions.
- Requires proper login/authentication flow to establish a valid Telegram session before executing operations.
Troubleshooting
Session Closed or Unauthorized Errors:
If the error message indicates that the client session is closed or unauthorized, it means the Telegram session has expired or was terminated. The user must re-authenticate using the login process described at https://telepilot.co/login-howto.Invalid Chat ID or Message ID:
Providing incorrect or non-existent chat or message IDs will likely cause errors or empty results. Verify IDs carefully.Command Not Supported or Unexpected Auth State:
During login, if unexpected commands or states occur, follow the instructions provided by the node's login help commands or consult the documentation link.Network or API Limitations:
Ensure network connectivity and that the Telegram API limits are respected to avoid throttling or failures.
Links and References
- TelePilot Login Guide — Instructions for authenticating and managing Telegram sessions.
- Telegram Bot API Documentation — Official Telegram API reference (general context).
- TelePilot GitHub Repository (if publicly available) — Source code and additional resources.
This summary focuses on the Message - Get Messages operation and its relevant input/output based on the provided source code and property definitions.