Telegram CoPilot Trigger icon

Telegram CoPilot Trigger

Your Personal Telegram CoPilot Listener

Telegram CoPilot Trigger

AI-generated

Overview

This node acts as a trigger for Telegram events using the TelePilot API. It listens for specified Telegram events such as new messages, message edits, deletions, chat actions, and user status updates. When an event occurs, it emits the event data for further workflow processing. This node is useful for automating responses or actions based on Telegram activity, such as monitoring chats for new messages or tracking user status changes.

Use Case Examples

  1. Automatically respond to new messages in a Telegram chat.
  2. Log message edits or deletions for audit purposes.
  3. Trigger workflows based on user status updates or chat actions.

Properties

Name Meaning
Events Specifies which Telegram events to listen for. Options include all events (*), Chat Action, Message Deleted, Message Edited, New Message, and User Status. Default is New Message.

Output

JSON

  • _ - Type of the Telegram event received, e.g., NewMessage.
  • message - The Telegram message object related to the event, converted to a JSON-friendly format.
  • chat - The chat entity information related to the message, converted to a JSON-friendly format.

Dependencies

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

Troubleshooting

  • If the Telegram account is not logged in, the node emits an error message advising to use the ChatTrigger node with phone number login and refers to the TelePilot login guide.
  • Timeout error occurs if no message is received within 30 seconds during manual trigger execution; this timeout does not apply to active workflows which listen indefinitely.
  • Errors fetching chat entity information are logged but do not stop event processing.

Links

  • TelePilot Login Guide - Guide for logging in to Telegram using TelePilot API with phone number authentication.

Discussion