Telegram publish
Deliver reviewed content to a configured Telegram destination.
Inputs
| Field | Type | Contract |
|---|---|---|
| text * | string | Message body. In shipped loops this is a prior step's output, templated into api-request body. |
Outputs
| Field | Type | Contract |
|---|---|---|
| sent | boolean | Recipe surface, not an engine field. True when the api-request completed; false when the file sink was used instead. |
| chatId | string | Optional. The chat that was addressed. Not an engine field — the request body carries chat_id. |
Behavior and limits
A named recipe over api-request, not a new engine kind. POSTs to Telegram sendMessage with {{env.TELEGRAM_BOT_TOKEN}} and {{env.TELEGRAM_CHAT_ID}}. The runner still executes api-request (). Unset env vars do not fire a URL with braces in it — the runner writes to .qf/out/ and says so (SPEC §9).
Try it in context
Use the linked loops to inspect actual configuration and how output is passed to the next step. Keep credentials in your local environment.
Validation and run evidence
Run evidence not supplied. Release acceptance: pending.
No new validation or execution is performed by viewing this page.
No output artifact is available for this material.
Loops using this component
- Draft, check, approve, publish
Prepare a post and pause for your approval before publishing.
- Content feed
Read an RSS feed, write a short morning digest and send it to Telegram. Repeated runs may redeliver; receiver-side deduplication requires separate configuration.
Explore example uses
Illustrative scenarios based on these loops. These are ideas to adapt, not verified customer results.
- From sources to a story
Turn selected sources into a cited story you can review before delivery.
- An inbox that reads itself
Turn a source feed into a reading queue with enough context to choose.
- One brief. A better first draft.
A launch draft grounded in the product brief and its actual capabilities.
- Less blank-page Monday
Shape a week of content around one brief and a clear audience.
- Publish after the yes
Keep the exact draft you approved tied to its delivery.
- A quieter daily routine
Bring routine updates together before you start the day.
Recorded examples
One prompt to your result
Your agent handles setup, configuration and checking the result in your project.