Overview
This node acts as a trigger for Telegram updates using the TelePilot API, allowing workflows to listen for various Telegram events in real-time. It is particularly useful for automating responses or actions based on incoming messages, chat changes, notifications, and many other Telegram update types.
Common scenarios include:
- Automatically processing new messages or edited messages.
- Reacting to chat title or photo changes.
- Monitoring user status or group call events.
- Handling custom queries or inline callbacks from Telegram bots.
For example, you could use this node to start a workflow whenever a new message arrives in a Telegram chat, enabling automated replies or logging.
Properties
| Name | Meaning |
|---|---|
| Events | Select one or multiple Telegram update event types to listen for. Options include a wide range of Telegram update events such as: NewMessage, MessageEdited, ChatTitle Updated, UserStatus, PollAnswer, NewChatJoinRequest, and many more. Selecting "*" listens to all events. |
Output
The node outputs JSON data representing the Telegram update event received. Each output item contains a single object with the raw update data under the json field. The structure of this data depends on the specific Telegram update event triggered.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for the TelePilot Telegram API, including necessary authentication details like API ID, API hash, and phone number.
- Uses the TelePilot Node Connection Manager internally to manage client sessions and authentication.
- Requires proper configuration of the Telegram API credentials within n8n.
Troubleshooting
- Not logged in error: If the Telegram account is not logged in, the node emits a message instructing to use a separate login node with phone number authentication. Ensure that the Telegram account is properly authenticated before triggering this node.
- Timeout on manual trigger: When running the node manually, if no matching update is received within 30 seconds, it will abort with a timeout error. This does not affect active workflows which listen indefinitely.
- Event filtering: If no events are selected or the filter does not match incoming updates, the node will not emit any data. Verify that the correct event types are selected.
- Connection issues: Errors related to connection or authentication will be logged via debug messages. Check API credentials and network connectivity.
Links and References
- TelePilot Login Guide — Instructions for authenticating your Telegram account.
- Telegram Bot API Documentation — Reference for Telegram update event types and structures (for understanding event payloads).