Short answer: Drop the "Telegram → Send Poll" 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: -100123456789 |
Question question | string | Required | Question. Example: What should we have for lunch? |
Options (JSON array) options | string | Required | Array of answer options (2-10) |
Anonymous is_anonymous | options | Optional | Anonymous. Options: Yes, No |
Multiple Answers allows_multiple_answers | options | Optional | Multiple Answers. Options: No, Yes |
{"chat_id": "e.g. -100123456789","question": "e.g. What should we have for lunch?","options": "[\"Pizza\", \"Sushi\", \"Tacos\", \"Salad\"]","is_anonymous": "{{trigger.is_anonymous}}","allows_multiple_answers": "{{trigger.allows_multiple_answers}}"}
{"ok": true,"result": {"poll": {"id": "poll123","options": [{"text": "Pizza","voter_count": 0}],"question": "What for lunch?"},"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.