Telegram CoPilot Trigger icon

Telegram CoPilot Trigger

Your Personal Telegram CoPilot Listener

Overview

The Telegram CoPilot Trigger node listens for real-time Telegram updates (events) using the TelePilot API. It acts as a personal Telegram listener that triggers workflows whenever specified Telegram events occur. This node is useful for automating responses or processing data based on Telegram activity, such as new messages, message edits, chat updates, notifications, and many other Telegram update types.

Common scenarios:

  • Automatically processing incoming Telegram messages to trigger further workflow actions.
  • Monitoring specific Telegram events like message sends, edits, or user status changes.
  • Filtering out group chat events if desired.
  • Integrating Telegram updates into broader automation pipelines without manual polling.

Practical example:

  • A workflow that triggers when a new message arrives (updateNewMessage) and automatically logs the message content or sends an alert.
  • Listening for chat title changes (updateChatTitle) to update records in a CRM system.
  • Ignoring group chat events while monitoring direct messages only.

Properties

Name Meaning
Events The Telegram update event types to listen for. Multiple options can be selected. Includes all Telegram update events such as updateNewMessage, updateMessageContent, updateChatTitle, updateUserStatus, etc. Selecting * listens to all events. Default is updateNewMessage and updateMessageContent.
Options Additional settings for the trigger node. Currently supports:
• Ignore Groups Events: When enabled, events related to negative chat IDs (usually groups) are ignored, so only individual chats trigger the workflow.

Output

The node outputs JSON objects representing the raw Telegram update events received from the TelePilot client. Each output item corresponds to one Telegram update event matching the selected filters.

  • The JSON structure varies depending on the event type but always includes a property _ indicating the update type (e.g., "updateNewMessage", "updateChatTitle").
  • The full event data is passed through, allowing workflows to access detailed information about messages, chats, users, notifications, and more.
  • No binary data output is produced by this node.

Dependencies

  • Requires an API key credential with Telegram API credentials (apiId, apiHash, and phoneNumber) to authenticate with the TelePilot service.
  • Uses the TelePilot Node Connection Manager internally to manage client sessions and listen for Telegram updates.
  • The node depends on the TelePilot API and its underlying TDLib-based update events.
  • Requires proper configuration of the Telegram API credentials in n8n before use.

Troubleshooting

  • Not logged in error: If the Telegram account is not logged in, the node emits an error message instructing to use a login node/action first. Ensure the Telegram API credentials are valid and the phone number login process has been completed.
  • No events received: Check that the selected events include those you expect to receive. Using * listens to all events.
  • Ignoring group events: If no events appear and "Ignore Groups Events" is enabled, verify whether the updates come from group chats (negative chat IDs). Disable this option if group events are needed.
  • 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.
  • Connection issues: Errors from the TelePilot client are logged; ensure network connectivity and valid credentials.

Links and References

Discussion