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, users, messages, groups, files, and login sessions. Specifically, the "Mark Chat as Unread" operation allows users to toggle whether a particular chat is marked as unread in their Telegram account.
Common scenarios for this node include:
- Automating message management by marking important chats as unread to revisit later.
- Managing chat states programmatically in workflows that monitor or respond to Telegram activity.
- Integrating Telegram chat status updates into broader automation pipelines.
For example, you could use this node to mark a chat as unread when a certain keyword appears in a message, prompting manual follow-up later.
Properties
| Name | Meaning |
|---|---|
| Chat ID | The unique identifier of the Telegram chat to operate on (e.g., "122323"). |
| Mark as Unread? | Boolean flag indicating whether to mark the chat as unread (true) or read (false). |
Output
The node outputs an array of JSON objects representing the result of the invoked Telegram API method. For the "Mark Chat as Unread" operation, the output JSON typically contains the updated chat state reflecting whether it is marked as unread.
The exact structure depends on the Telegram API response but generally includes fields related to the chat's metadata and its unread status.
No binary data output is produced by this operation.
Dependencies
- Requires an active Telegram API credential configured in n8n, including necessary authentication tokens.
- Depends on the TelePilotNodeConnectionManager internal service to manage Telegram client sessions.
- Requires the user to be logged in to Telegram via the node’s login operations before performing chat operations.
Troubleshooting
- Session Not Logged In: If the Telegram session is not logged in or has expired, errors like "Please login" or "Session was closed or terminated" will occur. Resolve by running the login operation first.
- Unauthorized Errors: These indicate invalid or expired credentials; re-authenticate using the login flow.
- Invalid Chat ID: Providing a wrong or non-existent chat ID may cause errors or empty responses.
- Network Issues: Connectivity problems can cause failures invoking Telegram API methods.
- Command Not Supported: Using unsupported commands in login or other operations will return guidance messages.
Links and References
- TelePilot Login Guide — Instructions for logging in and managing Telegram sessions.
- Telegram Bot API Documentation — General reference for Telegram API methods (note: TelePilot uses TDLib internally, which differs somewhat).