Answer Telegram Callback
Acknowledge a Telegram inline button callback query with optional notification text.
Telegram Bot API provider for bot identity, project-scoped communication profile messaging, webhook ingress, and diagnostics.
Connection facts
These details come from the current StackOS provider manifest and action catalog. They describe the available connection—not a promise that every workflow will use every action.
Action catalog
Actions listed for this integration. Individual descriptions note availability limits. A workflow still decides which actions belong in the job and where approval is required.
12 matching actions
Acknowledge a Telegram inline button callback query with optional notification text.
Delete an explicit Telegram message reference when Telegram permits the bot to delete it.
Remove a Telegram webhook for a project-scoped communication profile.
Download a Telegram bot file_id into a generated StackOS artifact for inspected or forwarded media.
Verify a Telegram bot token and return safe bot identity metadata.
Read safe Telegram webhook status for a communication profile.
Bounded diagnostic getUpdates call for setup/debugging only; it does not normalize updates, store resources, or create agent requests.
Send a Telegram bot text message to an explicit allowed chat reference, with optional reply markup.
Send a Telegram bot photo/image message from a file id, public URL, or StackOS artifact ref.
Set a native Telegram emoji reaction on an explicit Telegram message reference.
Set the Telegram webhook URL for a communication profile after deployment and secret-token verification are configured.
Send one Telegram file/photo with caption as one message, or send 2-10 files as a Telegram media group.
Direct answer
People continue using Telegram Bot as their tool. StackOS adds it to a visible workflow, keeps the work in order, and passes only the approved action to the integration when that stage is ready.
Common questions
The current catalog includes 12 Telegram Bot actions across Agent Triggering, Messaging. The exact actions used depend on the workflow and approval rules.
No. Telegram Bot remains the tool that performs its part of the job. StackOS organizes the workflow, keeps status and dependencies visible, and calls the tool only when the plan reaches the right approved action.