Open app

DocumentationWorkflowsTriggers

Telegram · New update node

Starts the workflow for new messages, commands, channel posts, or button clicks received by your Telegram bot. The secure bot webhook is configured automatically in Production. Learn how to configure it, map inputs and outputs, run a test and resolve common errors.

7 min readUpdated

What this node does

Starts the workflow for new messages, commands, channel posts, or button clicks received by your Telegram bot. The secure bot webhook is configured automatically in Production.

Use Telegram · New update as a clearly defined step in an anymize workflow.

  • Starts a new workflow run.
  • Provides one output for following steps.
  • Runs as a regular step in the flow.

Set up the node

  1. 01Open a workflow and add Telegram · New update from the node catalog.
  2. 02Complete the required fields and map values from previous steps.
  3. 03Run the node with a small test record and inspect its output.
  4. 04Connect the successful output and activate the workflow after an end-to-end test.

Operations and modes

Telegram · New update has one focused purpose. Its available settings appear when you select the node.

Settings

FieldMeaningArea
Telegram botChoose the bot token from Workflow Secrets. @BotFather issues it directly; you do not need to register an OAuth app.Protected
Update typesJSON list of Telegram updates allowed to start this workflow. Leave empty or use [] for Telegram's default selection.Standard
Only bot commandOptional. Starts only when message text begins with this command. Include the leading /.Standard
Only chat IDOptional. Restricts the trigger to one private chat, group, or channel.Standard
Ignore messages from other botsPrevents bot-to-bot loops. Updates without a sender are unaffected.Standard

Inputs and outputs

InputMeaningType
StandardThis trigger does not require an input.JSON
OutputMeaningType
Event typeThe detected Telegram update type, such as message or callback_query.text
Update IDConfigure this value in the node panel.number
Chat IDConfigure this value in the node panel.text
Message IDConfigure this value in the node panel.number
Topic IDConfigure this value in the node panel.number
TextConfigure this value in the node panel.text
Media captionConfigure this value in the node panel.text
SenderThe Telegram user or bot that caused the update.json
ChatThe Telegram chat, group, or channel for this update.json
Button clickThe full Callback Query when an inline button is clicked.json
Callback dataThe data value from the clicked inline button.text
Raw updateThe complete Telegram update without losing information.json

Example and test run

Example incoming Telegram message: begin with a small, recognizable record. Inspect the output and only map fields that are present there.

Test-run example

{
  "event_type": "message",
  "update_id": 836521004,
  "chat_id": "-1001234567890",
  "message_id": 42,
  "message_thread_id": null,
  "text": "/status Produktion",
  "caption": null,
  "from": {
    "id": 118922110,
    "is_bot": false,
    "first_name": "Mara",
    "username": "mara_ops"
  },
  "chat": {
    "id": -1001234567890,
    "title": "Operations",
    "type": "supergroup"
  },
  "callback_query": null,
  "data": null,
  "update": {
    "update_id": 836521004
  }
}

Access and security

Before activation, review which data enters this step and what its output contains.

Store keys and credentials in the protected connection manager. Never paste them into normal workflow fields, test data or descriptions.

Troubleshooting

  • No output: inspect the latest run and confirm that the previous node returned the expected fields.
  • Empty variable: open the previous step output and use a field name from the real test data.
  • Workflow does not start: activate it and check the trigger's test and production mode.

Related articles