Telegram CoPilot Trigger icon

Telegram CoPilot Trigger

Your Personal Telegram CoPilot Listener

Overview

The Telegram CoPilot Trigger node listens for real-time events from a connected Telegram account using the TelePilot API. It acts as a trigger in n8n workflows, firing whenever selected Telegram update events occur (such as new messages, chat updates, user status changes, etc.). This node is ideal for automating workflows based on Telegram activity, such as forwarding messages, monitoring group chats, or responding to specific user actions.

Practical examples:

  • Start a workflow when a new message arrives in a Telegram chat.
  • Monitor and react to changes in chat titles or photos.
  • Trigger notifications or data processing when users join or leave groups.

Properties

Display Name Type Description
Events multiOptions Select one or more Telegram event types to listen for. The node will trigger when any of these events occur.

Events:
A comprehensive list of Telegram update events is available, including but not limited to:

  • NewMessage
  • MessageSendSucceeded
  • ChatTitle Updated
  • UserStatus
  • FileDownload
  • Poll
  • NewChatJoinRequest
    ...and many more.
    You can select all events by choosing "*".

Output

The node outputs a JSON object representing the raw Telegram update event that triggered the workflow. The structure of this object depends on the type of event received, but it always includes a property named _ indicating the event type (e.g., "updateNewMessage", "updateChatTitle").

Example output:

{
  "_": "updateNewMessage",
  "message": {
    "id": 12345,
    "chat_id": 67890,
    "content": {
      "text": "Hello!"
    },
    ...
  }
}
  • The exact fields vary depending on the event type.
  • No binary data is produced; only JSON objects are emitted.

Dependencies

  • TelePilot API credentials: You must provide valid apiId, apiHash, and phoneNumber via the telePilotApi credential in n8n.
  • External Service: Requires access to the TelePilot backend and Telegram's TDLib.
  • n8n Configuration: No special configuration beyond setting up the required credentials.

Troubleshooting

Common issues:

  • Not logged in: If your Telegram account is not authenticated, the node will emit an error message:

    Telegram account not logged in. Please use ChatTrigger node together with loginWithPhoneNumber action. Please check our guide at https://telepilot.co/login-howto

    Resolution: Use the ChatTrigger node with the loginWithPhoneNumber action to authenticate your Telegram account as described in the linked guide.

  • Timeout in manual mode: When running the node manually (e.g., during testing), if no event is received within 30 seconds, you may see:

    Aborted, no message received within 30secs. This 30sec timeout is only set for "manually triggered execution". Active Workflows will listen indefinitely.

    Resolution: Trigger the relevant event in Telegram within 30 seconds, or run the workflow as an active workflow for continuous listening.

  • Credential errors: Invalid or missing API credentials will prevent the node from connecting.

Links and References

Discussion