Telegram Inbound

purpose to receive and process messages sent to a telegram bot using an inbound webhook this node acts as a trigger in your workflow — activating whenever a user sends a message to your configured telegram bot problem statement many workflows need to capture incoming telegram messages to automate responses, analyze content, or trigger follow up actions without an integrated inbound trigger, this requires manual webhook setup or external services the telegram inbound node simplifies this by automatically connecting your bot to receive and process incoming telegram events directly inside your workflow requirements must have a valid telegram bot token created via @botfather should register a webhook url to receive telegram updates must support message metadata (e g , username, chat id, message text) should verify webhook registration status and token validity must output structured message data for downstream nodes use cases trigger automated replies or workflows when users message your bot log chat messages or user info into a database route telegram commands (e g , /start, /help) to logic flows integrate telegram with support systems or notifications combine with “send telegram message” node for interactive bots outcome captures telegram messages (text, command, or media) and outputs structured data for further automation — making it easy to create conversational workflows how to use 1\ add telegram inbound node drag the telegram inbound node into your workflow it acts as the entry trigger , so place it at the start of your automation 2\ configure bot token enter the bot token obtained from @botfather click test token to verify that the bot is reachable if successful, your bot is ready to connect 3\ webhook url this is the unique endpoint where telegram will send incoming updates the url is automatically generated for your bot instance click register webhook to link your bot to this url click check status to confirm if the webhook is active 4\ available data once registered, the node automatically extracts and provides structured data fields for use in your workflow node output output variable automatically generated (available directly in downstream nodes) output format json object containing message and user data