Overview
The "Telegram CoPilot Trigger" node listens for real-time Telegram updates based on selected event types. It connects to a Telegram account using provided API credentials and emits data whenever specified Telegram events occur. This node is useful for automating workflows triggered by Telegram activities such as new messages, message edits, chat updates, notifications, and many other Telegram update events.
Practical examples include:
- Automatically processing or responding to new incoming Telegram messages.
- Tracking changes in chat titles or permissions.
- Monitoring user status or group call events.
- Reacting to specific Telegram notifications or file downloads.
This node continuously listens for updates unless run in manual mode, where it waits up to 30 seconds for an event before timing out.
Properties
| Name | Meaning |
|---|---|
| Events | Select one or multiple Telegram update event types to listen for. Options include all Telegram update events such as updateNewMessage, updateMessageContent, updateChatTitle, updateUserStatus, updateFileDownload, and many more. Selecting * listens to all events. |
Output
The node outputs JSON objects representing the raw Telegram update events received from the Telegram client. Each output item contains a single property _ which holds the update event object with detailed information depending on the event type.
The node does not output binary data.
Dependencies
- Requires a valid Telegram API key credential including API ID, API hash, and phone number for authentication.
- Uses an internal connection manager to handle Telegram client sessions.
- Requires network access to Telegram servers.
- The node depends on the external TelePilot service/library for managing Telegram connections and updates.
Troubleshooting
- Not logged in error: If the Telegram account is not logged in, the node emits a message instructing to use a separate login node with phone number authentication. Ensure proper login before triggering this node.
- Timeout in manual mode: When running manually, if no event is received within 30 seconds, the node throws a timeout error. This is expected behavior; increase wait time or run the workflow actively to listen indefinitely.
- Connection issues: Network problems or invalid credentials can prevent connecting to Telegram. Verify API credentials and network connectivity.
- Event filtering: If no events are emitted, check that the selected event types match the actual Telegram updates being generated.
Links and References
- TelePilot Login Guide - Instructions for logging into Telegram via TelePilot.
- Telegram API documentation (for understanding update event types): https://core.telegram.org/tdlib/docs/