Short answer: Drop the "Telegram → Edit Message Text" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Chat ID chat_id | string | Required | Chat ID |
Message ID message_id | string | Required | Message ID |
New Text text | string | Required | New Text |
Parse Mode parse_mode | options | Optional | Parse Mode. Options: HTML, Markdown, None |
{"chat_id": "{{trigger.chat_id}}","message_id": "{{trigger.message_id}}","text": "{{trigger.text}}","parse_mode": "{{trigger.parse_mode}}"}
{"ok": true,"result": {"text": "Updated text","message_id": 123}}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.