Overview

This node listens for new messages from Telegram using the MTPROTO API. It establishes a connection to Telegram with provided credentials and triggers workflows when new messages are received. It supports both automatic event-driven triggering and manual triggering with a timeout. This node is useful for automating responses, monitoring chats, or integrating Telegram messages into other workflows.

Use Case Examples

1. Automatically process incoming Telegram messages in a customer support workflow.
2. Trigger notifications or actions based on specific Telegram chat messages.
3. Manually trigger a workflow to wait for a Telegram message within a set timeout period.

Output

JSON

• peer - The Telegram entity (user, group, or channel) from which the message originated.
• message - The content and metadata of the received Telegram message.
• isGroup - Boolean indicating if the message is from a group chat.
• isChannel - Boolean indicating if the message is from a channel.
• isPrivate - Boolean indicating if the message is from a private chat.
• chat - Additional chat information related to the message.

Dependencies

• Telegram MTPROTO API credentials for authentication

Troubleshooting

• Connection errors typically indicate invalid credentials or lack of authorization. Verify the Telegram API credentials and ensure the application is authorized to access the Telegram account.
• Timeout errors during manual triggering mean no message was received within 30 seconds. Ensure messages are being sent to the monitored chat or increase the timeout if needed.
• Errors adding or removing event handlers may occur if the Telegram client connection is unstable. Restarting the node or re-authenticating may help resolve these issues.