Telegram Bot MCP integration for AI agents.
Connect AI agents to Telegram Bot through 50 structured actions, including answer callback query, approve chat join request, ban chat member, and copy messag…
- ACTION CONTRACTS
- 50
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Telegram Bot integration exposes
The Telegram Bot Agent App exposes 50 provider-backed actions for communication and social work. Its current contract lets an authorized agent answer an inline keyboard callback query, approve a user's pending request to join a telegram chat, and ban a user from a group, supergroup, or channel. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Telegram Bot account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Telegram Bot capabilities.
Showing 12 of 50 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
answer_callback_queryREADAnswer an inline keyboard callback query.
INPUTS: callbackQueryId / text / showAlert / url / cacheTime
approve_chat_join_requestWRITEApprove a user's pending request to join a Telegram chat.
INPUTS: chatId / userId
ban_chat_memberHIGH IMPACTBan a user from a group, supergroup, or channel.
INPUTS: chatId / userId / untilDate / revokeMessages
copy_messageREVIEWCopy one message without linking back to the original message.
INPUTS: chatId / fromChatId / messageId / messageThreadId / caption
copy_messagesREVIEWCopy 1-100 messages without links to the originals while preserving album grouping.
INPUTS: chatId / fromChatId / messageIds / messageThreadId / disableNotification
create_chat_invite_linkWRITECreate an additional Telegram chat invite link with optional expiry or approval rules.
INPUTS: chatId / name / expireDate / memberLimit / createsJoinRequest
decline_chat_join_requestREVIEWDecline a user's pending request to join a Telegram chat.
INPUTS: chatId / userId
delete_business_messagesHIGH IMPACTDelete one or more messages on behalf of a connected Telegram business account.
INPUTS: businessConnectionId / messageIds
delete_messageHIGH IMPACTDelete a message from a chat.
INPUTS: chatId / messageId
delete_messagesHIGH IMPACTDelete 1-100 messages from one Telegram chat.
INPUTS: chatId / messageIds
delete_webhookHIGH IMPACTDelete the configured webhook and optionally drop pending updates.
INPUTS: dropPendingUpdates
edit_chat_invite_linkWRITEEdit an additional Telegram chat invite link created by the bot.
INPUTS: chatId / inviteLink / name / expireDate / memberLimit
INPUT CONTRACTS
Know what the action needs before it runs.
answer_callback_query
callbackQueryIdREQUIRED- The callback query ID to answer.
textOPTIONAL- The notification text to show to the user.
showAlertOPTIONAL- Whether to show an alert instead of a notification.
urlOPTIONAL- The URL to open for the callback query.
cacheTimeOPTIONAL- The maximum time in seconds that the result may be cached client-side.
approve_chat_join_request
chatIdREQUIRED- The target Telegram chat ID or channel username.
userIdREQUIRED- The user identifier from the join request.
ban_chat_member
chatIdREQUIRED- The target Telegram chat ID or channel username.
userIdREQUIRED- The target user identifier.
untilDateOPTIONAL- The Unix timestamp when the ban ends.
revokeMessagesOPTIONAL- Whether to delete all messages from the banned user.
copy_message
chatIdREQUIRED- The target Telegram chat ID or channel username.
fromChatIdREQUIRED- The target Telegram chat ID or channel username.
messageIdREQUIRED- A Telegram message identifier.
messageThreadIdOPTIONAL- The target forum topic identifier.
captionOPTIONAL- A replacement media caption.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Answer Callback Query
Answer an inline keyboard callback query. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
answer_callback_queryControl Approve Chat Join Request
Approve a user's pending request to join a Telegram chat. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
approve_chat_join_requestVerify with Approve Chat Join Request
Approve a user's pending request to join a Telegram chat. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
approve_chat_join_requestSAFETY BOUNDARY
Operate Telegram Bot with explicit limits
- Authorize Telegram Bot with API key and grant only the provider access required by the selected actions.
- 28 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `ban_chat_member`, `delete_business_messages`, and `delete_message` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Telegram Bot rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Telegram Bot task completed successfully.
CONNECTION MODEL
API key
Create a new bot with @BotFather using /newbot, then paste the generated token here. Telegram documents BotFather at https://core.telegram.org/bots/features#botfather.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 11
- WRITE SIGNALS
- 22
- HIGH IMPACT
- 6
- REVIEW SIGNALS
- 11
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Telegram Bot.