Overview
This node acts as a trigger for Telegram updates using the Telegram CoPilot API. It listens for various Telegram events (such as new messages, message edits, chat updates, user status changes, etc.) and emits them as workflow triggers in n8n. This is useful for automating workflows based on real-time Telegram activity without polling.
Common scenarios include:
- Automating responses or logging when new messages arrive.
- Triggering workflows on message edits or deletions.
- Monitoring chat or user status changes to update external systems.
- Handling notifications or custom Telegram events dynamically.
For example, you could use this node to automatically save incoming Telegram messages to a database or notify a team via another channel whenever a specific event occurs.
Properties
| Name | Meaning |
|---|---|
| Events | Select one or more Telegram update event types to listen for. Options include all standard Telegram update events such as NewMessage, MessageEdited, ChatTitle Updated, UserStatus, PollAnswer, and many others. Selecting * listens to all events. Default is updateNewMessage and updateMessageContent. |
| Options | Additional options for the trigger: - Ignore Groups Events: If enabled, events related to group chats with negative chat IDs will be ignored. Useful to filter out group-related updates if not needed. |
Output
The node outputs JSON objects representing the raw Telegram update events received from the CoPilot API. Each output item corresponds to one Telegram update event matching the selected filters.
The structure of each JSON object varies depending on the event type but generally includes an _ property indicating the update type (e.g., updateNewMessage) and other relevant fields describing the event details (message content, chat info, user data, etc.).
No binary data is output by this node.
Dependencies
- Requires a valid Telegram API authentication credential including API ID, API hash, and phone number.
- Uses the Telegram CoPilot API client managed internally by the node.
- The node depends on the
typedicontainer and internal connection manager classes for handling Telegram sessions. - Requires proper configuration of the Telegram API credentials in n8n before use.
Troubleshooting
- Not receiving any updates: Ensure that the Telegram account is properly logged in and authenticated. The node will emit an error message if the account is not logged in.
- Timeout on manual trigger: When running the node manually, it waits up to 30 seconds for an event before aborting. For continuous listening, run the workflow actively instead of manual execution.
- Ignoring group events: If no events appear and "Ignore Groups Events" is enabled, verify whether your updates are coming from group chats (negative chat IDs). Disable this option if you want to receive group updates.
- Authentication errors: Check that the provided API credentials (API ID, API hash, phone number) are correct and have the necessary permissions.
- Unhandled event types: If you select specific events but do not see expected outputs, confirm that those event types are actually being emitted by Telegram for your account.
Links and References
- Telegram API Documentation
- Telegram CoPilot Official Site
- Telegram Login Guide (as referenced in the node's error message)