Telegram Advance Trigger
AI-generatedSummary
Starts the workflow when a Telegram update of the selected types arrives, optionally filtered by allowed chat/user IDs. The trigger shares a single getUpdates stream per bot with the Telegram Advance question node, so a trigger and a waiting question can run on the same bot without a 409 Conflict. No public URL is needed. In n8n queue mode, configure Redis in the credentials so one worker polls and the others read updates from Redis — without Redis each worker polls independently and may 409.
Inputs
- updates — Which Telegram update types start the workflow. Default: ['message']. Type: multiOptions with options: Callback Query (Button Press), Channel Post, Edited Channel Post, Edited Message, Message.
- allowedIds — Optional comma-separated list of chat IDs or user IDs. When set, only updates from a matching chat or sender start the workflow. Leave empty to accept all. Type: string, placeholder: '123456789, -1001234567890'.
Output shape
object
Emits the raw Telegram update object (the full update payload) that passed the type and ID filters via the main output.
Examples
Example 1: A user sends a message to the bot; the trigger fires and passes the message update to the next node.
Updates: ['message']; Allowed Chat/User IDs: (empty)