Short answer: Drop the "Telegram → Send Message" 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. Example: 123456789 or @channelusername |
Message Text text | string | Required | Message Text |
Parse Mode parse_mode | options | Optional | Parse Mode. Options: None (plain text), HTML, MarkdownV2 |
Silent disable_notification | options | Optional | Silent. Options: No, Yes |
{"chat_id": "e.g. 123456789 or @channelusername","text": "{{trigger.text}}","parse_mode": "{{trigger.parse_mode}}","disable_notification": "{{trigger.disable_notification}}"}
{"ok": true,"result": {"chat": {"id": 456,"type": "private"},"text": "Hello!","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.