Short answer: Drop the "Telegram → Send Photo" 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 |
Photo URL photo | string | Required | Photo URL. e.g. "https://example.com/image.jpg" |
Caption caption | string | Optional | Caption |
{"chat_id": "{{trigger.chat_id}}","photo": "https://example.com/image.jpg","caption": "{{trigger.caption}}"}
{"ok": true,"result": {"photo": [{"width": 100,"height": 100,"file_id": "abc"}],"message_id": 124}}
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.