Actions40
- Chat Actions
- Custom Request Actions
- Group Actions
- File Actions
- Login Actions
- Message Actions
- User Actions
- Contact Actions
Overview
This node operation allows marking a Telegram chat as unread or read. It is useful for managing chat notifications and ensuring important chats are flagged for attention. For example, a user can mark a chat as unread to remind themselves to revisit it later or to signal to others that the chat requires attention.
Use Case Examples
- Mark a specific chat as unread to keep track of pending messages.
- Toggle the unread status of a chat based on user interaction or workflow logic.
Properties
| Name | Meaning |
|---|---|
| Chat ID | The unique identifier of the chat to be marked as unread or read. |
| Mark as Unread? | Boolean flag indicating whether the chat should be marked as unread (true) or read (false). |
Output
JSON
_- The response object from the Telegram API indicating the result of the toggle operation, including the updated chat status.
Dependencies
- Requires an API key credential for Telegram API access.
Troubleshooting
- Ensure the Telegram API credentials are valid and the session is active; otherwise, the node will throw login-related errors.
- If the chat ID is invalid or the user lacks permission, the Telegram API may return errors that should be handled appropriately.
- Common error messages include 'Please login' indicating the need to authenticate, and 'Session was closed or terminated' indicating the session must be re-established.
Links
- TelePilot Login Guide - Instructions for logging in and managing Telegram sessions with TelePilot.