Actions27
- Chat Actions
- File Actions
- Group Actions
- Message Actions
- User Actions
Overview
This node integrates with Telegram via the TelePilot API, enabling automation and interaction with Telegram chats, messages, users, groups, and files. Specifically, the Get Chat History operation fetches the message history of a specified chat starting from a given message ID. This is useful for scenarios such as archiving conversations, analyzing chat content, or syncing messages to other systems.
Practical examples:
- Retrieve the latest messages from a customer support chat to analyze user inquiries.
- Fetch historical messages from a group chat for compliance or record-keeping.
- Automate monitoring of chat activity by periodically fetching new messages.
Properties
| Name | Meaning |
|---|---|
| Chat ID | The unique identifier of the chat whose history you want to retrieve. |
| From Message ID | The message ID from which to start fetching history; use "0" to start from the most recent message. |
Output
The node outputs an array of JSON objects representing the chat history messages retrieved. Each object corresponds to a Telegram message entity with detailed fields describing the message content, sender, timestamp, and other metadata as provided by the TelePilot API.
No binary data output is indicated for this operation.
Dependencies
- Requires an active Telegram API credential (an API key and authentication token) configured in n8n.
- Depends on the TelePilot Node Connection Manager to handle Telegram client sessions and API calls.
- The Telegram account must be logged in and authorized; otherwise, the node will prompt for login or throw errors indicating the need to authenticate.
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 flow described at https://telepilot.co/login-howto.Invalid Chat ID or Message ID:
Providing incorrect or non-existent chat or message IDs may result in empty results or errors. Verify IDs are correct and accessible by the authenticated Telegram account.Rate Limits or API Errors:
Excessive requests or invalid parameters might cause API errors. Ensure proper usage and respect Telegram API limits.
Links and References
- TelePilot Login Guide — Instructions for authenticating your Telegram account.
- Telegram Bot API Documentation — For understanding Telegram message and chat structures (note: TelePilot uses TDLib but concepts overlap).
- TelePilot Official Site — Additional resources and support for the TelePilot integration.