Telegram Ops Airlock for RailCall marketplace README

Telegram Ops Airlock

Install slug: amadey/telegram

If Telegram is part of your day-to-day operations — handling alerts, running a paid community, or managing moderation — this is built for teams like yours.

You want your automation to take real actions in Telegram: send a message, ban a member, create an invite link. But every action should be visible to you first, with your approval required before anything happens. Nothing runs on its own.

20 commands across three areas: inspect Telegram (chats, members, admins), manage messages (send, edit, delete, forward, pin — including photos and files), and control access (invites, join requests, ban, unban, mute, promote).

Requirements

• RailCall Station v1.5.0+ (v2 tree-signed module bundle)
• Bot token from @BotFather in Integrations → telegram_bot
• Bot already a member of the target chat; admin rights for pin, invites, join requests, ban, mute, promote
• Use vault provider telegram_bot, not catalogue telegram (on Windows the catalogue slot can break credential receipt paths)

Install

railcall market install amadey/telegram

Studio → Modules → Reload all.

Credentials

Integrations → telegram_bot → BotFather token → Test (calls Telegram getMe).

What it looks like in practice

Deploy fails

The bot posts in the chat right away. When it's fixed, the same message changes to say FIXED — it doesn't post a new one. You can pin it while people are working on the fix.

{
  "chat_id": "-1001234567890",
  "text": "FAIL deploy production — waiting triage",
  "parse_mode": "HTML"
}

Take message_id from the send receipt → edit_message_text / pin_chat_message / unpin_chat_message / delete_message.

Payment fails

The invite link is revoked and the person is removed from the group. Changed your mind? Unban brings them back.

Someone asks to join

You approve or decline right from RailCall — no need to open Telegram yourself.

Moderation

See who's in the chat. Mute or remove someone breaking the rules. Promote someone to admin if you need to. Every action still needs your yes first.

Also: resolve_chat_id, get_chat, forward_message, send_photo, send_document.

Track B (bundled, not a separate marketplace listing yet)

The repo includes workflow spec workflows/deploy-fail-telegram-alert/ — one approved send_message when a deploy or agent run fails. Import the JSON in Studio locally; a separate workflow marketplace listing may follow later.

Security

Token only via vault_get("telegram_bot"). Writes need approval and leave a signed receipt. Network: api.telegram.org only.

Limitations

No inbound webhooks, AI chat, forums/topics, polls, or bulk broadcast. The bot has to already be in the chat.
send_document / send_photo need a local file path on the Station host.
resolve_chat_id reads recent bot updates (message / channel_post only) — message the bot first if the list is empty.
kick_chat_member bans (blacklists) the member — it's not a temporary kick. Call unban_chat_member right after if you want them able to rejoin.

contest:2026Q3