Actions40
- Chat Actions
- Custom Request Actions
- Group Actions
- File Actions
- Login Actions
- Message Actions
- User Actions
- Contact Actions
Overview
This node integrates with Telegram via the TelePilot API, enabling various chat-related operations such as opening a chat, sending messages, retrieving chat history, managing chat members, and more. It is useful for automating Telegram interactions within workflows, such as opening a chat to start a conversation, sending media or text messages, or managing chat settings programmatically.
Use Case Examples
- Opening a chat by its ID to prepare for sending messages or retrieving chat details.
- Sending a text message or media file to a specific Telegram chat.
- Retrieving chat history or details for analysis or logging.
- Adding members to a chat or toggling chat unread status.
Properties
| Name | Meaning |
|---|---|
| Chat ID | The unique identifier of the Telegram chat to operate on. Required for operations like opening a chat, sending messages, or managing chat members. |
Output
JSON
chat_id- The ID of the chat involved in the operation.result- The result object returned from the Telegram API for the requested operation, which may include chat details, message information, or status responses.
Dependencies
- Requires an API key credential for TelePilot API authentication to interact with Telegram.
Troubleshooting
- Common issues include authentication errors such as 'Unauthorized' or 'Session was closed or terminated', which require re-login via the ChatTrigger node or following the login guide at https://telepilot.co/login-howto.
- Errors related to file handling when sending media messages, such as missing files or unsupported formats, require verifying file paths and formats.
- Telegram API errors like 'CHAT_WRITE_FORBIDDEN' indicate permission issues in the target chat, which need appropriate user permissions to resolve.
Links
- TelePilot Login Guide - Instructions for logging in and managing Telegram sessions with TelePilot.