Codex
Claude
GeminiWhat you do
- Provide the reply intent and approved media or action choices.
- Confirm any button behavior that creates work or changes state.
- Review the sent message and stored interaction refs.
Teams replying to Telegram requests with media or buttons / communications
Rich Telegram Reply
One Telegram reply whose text, media, buttons, and thread context match the approved response contract.
From request to resultA complete plan you can follow.
Visible planThe problem
Rich replies can silently lose images, buttons, threading, or privacy boundaries when a platform feature is unavailable.
What the agent does
- Load the originating request and Telegram surface policy.
- Validate text, every media item, and button payload before any send.
- Send without silent degradation and store message and interaction receipts.
When this workflow helps
A reusable method, adapted to the request.
- A Telegram message created an agent_request and the response may need buttons or images.
- The agent must respect the originating communication profile, chat, thread, and response policy.
Before it starts
Connection required
- A connected Telegram profile
- An originating request and approved reply destination
- Safe media refs and defined button behavior
What proves it worked
Evidence, not a success claim.
- Validated payload
- Telegram message and media ids
- Stored button interaction refs
Workflow path
The reusable stages of the work.
A real run expands these stages around the request, context, selected tools, approvals, and dependencies.
- 01Passes to next stage
Read Origin Context
Inspect the request metadata, communication profile guidance, and thread context.
- 02Passes to next stage
Compose Response Payload
Decide exact text, image refs, and optional button payloads without embedding secrets.
- 03Verified outcome
Send Telegram Response
Execute the explicit Telegram send action granted by the run plan.
Safe stopping and recovery
Useful even when the whole path cannot run.
- Stop with a validated reply packet when the origin or feature contract is incomplete.
- Reject unsupported rich features instead of silently dropping them.
- Use provider receipts and idempotency state to avoid duplicate replies after failure.
Specialists inside this workflow
Clear roles for each part of the job.
Connected work