Short answer: Drop the "Telegram → Send Animation/GIF" 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 |
Animation URL animation | string | Required | Animation URL |
Caption caption | string | Optional | Caption |
{"chat_id": "{{trigger.chat_id}}","animation": "{{trigger.animation}}","caption": "{{trigger.caption}}"}
{"ok": true,"result": {"message_id": 130}}
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.