Overview
This node acts as a trigger for Telegram events using the TelePilot API. It listens for specified Telegram update events and emits them as output, enabling workflows to react to real-time Telegram activities such as new messages, chat updates, user status changes, and more. It is useful for automating responses, notifications, or processing Telegram data based on live events.
Use Case Examples
- Trigger a workflow when a new message is received in Telegram.
- Listen for chat title updates to automate logging or notifications.
- React to user status changes to update presence information in another system.
Properties
| Name | Meaning |
|---|---|
| Events | Specifies which Telegram update events to listen for. Users can select multiple event types or all events using '*'. |
| Options | Additional options for the trigger behavior. |
Output
JSON
a- The Telegram update event data emitted by the trigger.
Dependencies
- TelePilot API
Troubleshooting
- If the node emits an error stating the Telegram account is not logged in, ensure the user has logged in using the appropriate phone number login method as per the TelePilot guide.
- If no events are received, verify that the selected events are correct and that the Telegram API credentials (apiId, apiHash, phoneNumber) are valid and active.
- If ignoring group events, ensure that the chat_id field is correctly set and that group events have negative chat_ids as expected.
Links
- TelePilot Login Guide - Guide for logging in to Telegram using TelePilot API.