Overview

This node acts as a trigger for Telegram CoPilot events, listening for various Telegram update events and emitting them as workflow triggers. It is useful for automating workflows based on real-time Telegram activities such as new messages, message edits, chat updates, and many other Telegram-specific events. For example, it can trigger a workflow when a new message is received or when a chat title is updated.

Use Case Examples

1. Trigger a workflow when a new Telegram message arrives to process or log the message.
2. Trigger a workflow when a chat's title or photo is updated to synchronize chat information elsewhere.
3. Trigger a workflow on specific Telegram events like message edits or user status changes for custom notifications or analytics.

Properties

Output

JSON

• _ - The type of Telegram update event received.
• message - The full message object related to the event, if applicable.
• ``
  • *
    * `` - Other properties depend on the specific Telegram update event type and contain detailed event data.

Dependencies

• Requires Telegram API credentials including apiId, apiHash, and phoneNumber for authentication.

Troubleshooting

• If the Telegram account is not logged in, the node emits an error message instructing to use a login node with phone number authentication.
• If the selected events do not include the incoming update type, no triggers will fire for those updates.
• If 'Ignore Groups Events' is enabled, events from group chats (negative chat IDs) will be ignored, which might cause expected triggers to not fire for group messages.
• Timeout error occurs if the node is manually triggered and no event is received within 30 seconds; this timeout does not apply to active workflows listening indefinitely.

Links

• Telegram CoPilot Login Guide - Guide for logging in to Telegram CoPilot using phone number authentication.