← Back to Skills Marketplace
9385
Downloads
9
Stars
0
Active Installs
15
Versions
Install in OpenClaw
/install telegram-api
Description
Telegram Bot API integration with managed authentication. Send messages, manage chats, handle updates, and interact with users through your Telegram bot. Use this skill when users want to send messages, create polls, manage bot commands, or interact with Telegram chats. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every `/telegram/` path goes to the Telegram Bot API and nowhere else; the methods documented here are the ones this skill uses, and the passthrough can also call other Bot API methods the bot token allows. Default to read calls, and confirm every send, edit, delete, or new connection with the user. This file also documents the three constructs that turn a Telegram Bot API connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Telegram Bot API action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Telegram Bot API examples; they add no Telegram Bot API capability - Telegram Bot API is not an event source, a trigger cannot read Telegram Bot API data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).
Usage Guidance
Install only if you intend to manage a Telegram bot through Maton. Pay special attention before approving message sends, deletes, setWebhook, trigger destinations, hosted functions, or raw API-key use, because those can create ongoing data flows or act on chats without further prompts if configured.
Capability Assessment
Credentials
The skill needs network access and managed authentication to call Telegram through Maton. Raw HTTP with a MATON_API_KEY is documented only as a fallback when the CLI cannot be installed, with warnings not to persist, print, or send the key elsewhere.
Install Mechanism
Installation uses pinned Maton CLI/package versions via npm or Homebrew and optional pinned SDK packages. This is proportionate for an API integration, but users should understand it installs a CLI and uses a Maton account.
Instruction Scope
The instructions repeatedly require user approval for connection creation, writes, deletes, hosted functions, trigger destinations, webhooks, and local event execution; external API content is explicitly treated as untrusted data.
Persistence & Privilege
Persistent elements include Maton login credentials in the OS credential store, Telegram connections, hosted functions, triggers, destinations, and Telegram webhooks. These are disclosed and paired with approval, scoping, and deletion guidance.
Purpose & Capability
The stated purpose is Telegram Bot API access through Maton, and the documented capabilities match that purpose: reading bot state, sending/editing/deleting messages, managing bot commands, webhooks, and optional automation via Maton functions and triggers.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install telegram-api - After installation, invoke the skill by name or use
/telegram-api - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.2.9
Simplify the login instructions to the code flow (maton login prints a link; finish with maton login --code <CODE>), drop the API Key subsection, and pin the Maton CLI install to 0.4.0.
v1.2.8
Switch the login instructions to the device flow (maton login prints a link and a user code; the --oauth flag is gone) and pin the Maton CLI install to 0.3.5.
v1.2.7
Pin the Maton CLI install to 0.3.4, the current release.
v1.2.6
Add this skill's own trigger policy to the shared Triggers section: the only destination it sets up is its own hosted function inside the platform, it does not forward events to third-party hosts, and it does not use event watch --exec; each trigger reference now also says this skill configures no trigger from that source on its own.
v1.2.5
Bring the skill to the current api-gateway baseline and tell the connection-to-function-to-trigger story: the shared Functions and Triggers sections open with an example for this app (a hosted function that performs one action for it through the Maton SDK, and the trigger that runs it - its own event source where it has one, otherwise a time schedule), the description says these constructs turn the connection into automation and add no capability of their own, the passthrough is described by its enforced boundary, CLI and SDK installs are pinned to 0.3.1, absolute API URLs are placeholders, and multipart uploads use mktemp.
v1.2.4
Stop documenting a download URL that requires the bot token. Telegram serves file bytes from api.telegram.org/file/bot<token>/<file_path>, and the old one-line note told the reader to use that path - which means obtaining the bot token and putting a live credential into a URL that lands in shell history, ps output, and proxy logs, contradicting this skill's own rule that the token never surfaces. The Files section now says not to construct it and to ask the user how a download should be authorized.
v1.2.3
Describe the actual boundary: a /telegram/ path is forwarded to the Telegram Bot API with the connection's bot token and cannot reach another host or another app's credential, so the passthrough widens to other Bot API methods rather than beyond Telegram. Adds the standing-egress warning on setWebhook that the routing reference already carried, and states that the raw-HTTP appendix is the same call over a different transport and manages no credential of its own.
v1.2.2
Fix the raw HTTP fallback example: restore the gateway base URL in the GATEWAY constant (and the fastmail streaming call), which a previous edit had replaced with a placeholder
v1.2.1
Address security-audit findings: disclose the api passthrough in the access-scope and description text, warn on irreversible connection deletion, add response data-minimization guidance, and correct app-specific auth and request-body notes
v1.2.0
CLI-first rewrite with the Maton SDK examples; clarify that the CLI and SDKs keep separate credential stores, and reword webhook egress warnings
v1.1.0
CLI-first rewrite: the maton CLI with OAuth login is the documented path, every example is a maton command, SDK examples added, and the raw HTTP fallback feeds the key on stdin instead of reading it from the environment
v1.0.3
- Changed API base URLs from gateway.maton.ai and ctrl.maton.ai to api.maton.ai throughout all usage examples and documentation.
- Updated the connection management instructions and endpoints to use the new base URL.
- Added a security and permissions section, clarifying resource access and the need for explicit user approval for write operations.
- Improved guidance for handling multiple Telegram connections with the Maton-Connection header.
- Removed the LICENSE.txt file.
v1.0.2
- Added a new `clawdbot` metadata block with an emoji and environment variables required (`MATON_API_KEY`) in SKILL.md.
- No changes to functionality or usage; documentation only.
v1.0.1
- No file changes detected in this release.
- Version number updated to 1.0.1.
- Documentation and skill functionality remain unchanged.
v1.0.0
Major update: rewritten for managed Maton API gateway integration and streamlined usage.
- Replaced in-depth, self-managed guide with direct instructions for using Telegram via the Maton API gateway.
- Added instructions for authentication with a Maton API key and simplified connection management.
- Removed all detailed Telegram workflow/reference documents.
- Included ready-to-use Python code examples for key operations (bot info, send message, manage connections).
- Centralized documentation to SKILL.md for ease of use; external references are no longer needed.
Metadata
Frequently Asked Questions
What is Telegram Bot?
Telegram Bot API integration with managed authentication. Send messages, manage chats, handle updates, and interact with users through your Telegram bot. Use this skill when users want to send messages, create polls, manage bot commands, or interact with Telegram chats. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every `/telegram/` path goes to the Telegram Bot API and nowhere else; the methods documented here are the ones this skill uses, and the passthrough can also call other Bot API methods the bot token allows. Default to read calls, and confirm every send, edit, delete, or new connection with the user. This file also documents the three constructs that turn a Telegram Bot API connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Telegram Bot API action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Telegram Bot API examples; they add no Telegram Bot API capability - Telegram Bot API is not an event source, a trigger cannot read Telegram Bot API data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe). It is an AI Agent Skill for Claude Code / OpenClaw, with 9385 downloads so far.
How do I install Telegram Bot?
Run "/install telegram-api" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Telegram Bot free?
Yes, Telegram Bot is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Telegram Bot support?
Telegram Bot is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Telegram Bot?
It is built and maintained by byungkyu (@byungkyu); the current version is v1.2.9.
More Skills