Telegram and Discord, wired into your tGate workspace.
Two bots, one workspace. Telegram for personal DMs and team groups. Discord for servers split between admin-only runbooks and customer-facing channels. Slash commands, incident pings, ticket threads, and one-tap actions — all bound to your tGate identity.
Telegram integration
Four steps. Two minutes.
- 1Open @BotFather in Telegram and run /newbot
- 2Give your bot a name and a unique @handle
- 3Paste the bot token below — we'll verify it on save
- 4Send /start to your bot to bind your tGate account
Bot token & identifiers.
Where messages land.
Telegram bot commands
Toggle which commands this bot exposes. Greyed-out commands aren't registered with the platform on save.
What this bot pushes to your DMs.
What it looks like in Telegram.
Mock-rendered using your current settings. "Send test message" above appends a real entry here and pushes to your bound chat (if connected).
⚙️ Control plane: OK
📈 Open incidents: 0
🎫 Open tickets: 3 — last reply 12m ago
ChatOps safe enough for production.
Bots that can page on-call or pause deploys are dangerous if you don't get the controls right. Here's how we handle it.
OAuth-bound, not token-shared
Each user authenticates with their tGate identity. Bot tokens never leave the workspace.
Signed webhooks
Inbound events use HMAC-SHA256 with rotating secrets. Verified before any side-effect runs.
Per-command audit log
Every slash command writes to the workspace audit log with actor, args, channel, and timestamp.
Approval gates for destructive ops
Sev-1 paging, deploy pause/resume, and token rotation require a second approver.
Quiet hours + dedupe
Repeating events collapse into one message; quiet hours suppress non-critical pings.
Revoke in one click
Disconnect a platform here — bots are uninstalled, tokens revoked, audit trail preserved.
Bring tGate into the room your team is already in.
Both bots are open-source. Self-host them or run them managed — same UX, same audit trail, same controls.