Short answer: Drop the "Telegram → Send Chat Action" 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 |
Action action | options | Required | Action. Options: Typing, Upload Photo, Upload Video, Upload Document, Record Voice |
{"chat_id": "{{trigger.chat_id}}","action": "{{trigger.action}}"}
{"ok": true,"result": true}
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.