Skip to content

Wiring a Telegram channel (admin)

Each calendar in the club can have a Telegram channel attached. When that’s set up, the bot posts to the channel on event changes, and families with the bot get phone notifications via Telegram.

This is an admin-only setup task. Once a channel is wired, all coaches benefit.

Prerequisites

  • A Telegram channel (not group) you control.
  • The bot account @teamsummitbot (or your club’s equivalent) added as an admin of that channel — required so it can post.

Telegram channel admin list with the bot added

Step by step

  1. From the coach top nav, go to Groups (admin only).
  2. Click into one of the groups under the calendar you’re wiring.
  3. Tap Telegram setup.
  4. Paste the channel’s channel_id (e.g. -1003388060864 — starts with -100). Telegram doesn’t expose this directly; you can get it from the @username_to_id_bot or via getUpdates after the bot posts once.
  5. (Optional) Paste an invite link (https://t.me/+...) — this is what families see on their chat panel for joining.
  6. Save.

Every group in the same calendar shares one channel. Wiring one group in a calendar wires the channel for all sibling groups too (post dedupe by channel_id).

Webhook (one-time)

After the channels are wired, register the bot’s webhook with Telegram so we receive channel posts:

curl -sX POST https://ts.onsnowlive.com/api/admin/telegram/webhook \
-H "cookie: __Host-coach_session=<your-session-token>" | jq

Returns { "ok": true, "webhook_url": "..." }. Now human admin posts in the channel flow into the family-page chat panel and trigger pushes.

Verifying

  • Post a manual message in the channel from the Telegram app.
  • Within ~1 second, reload a family page in the calendar’s groups — the post appears in the chat panel.
  • Families with push enabled get a phone notification.

Adding a second / third calendar

Repeat for each calendar. Three channels for Team Summit: one for Age Class, one for Ability, one for FIS — each wired to their own group_telegram row.

If a channel breaks (bot kicked, channel deleted)

A weekly probe runs every Monday morning and tests posting to each configured channel. If the bot has been kicked from a channel or the channel itself has been deleted, the probe writes an entry to /coach/feedback under the bot-health source — visible to all admins — with a short note pointing to the affected group.

Most common fix: re-add the bot as admin in the channel. If the channel is genuinely gone, remove the wiring from the group’s Telegram setup screen to stop the weekly alarm.

You don’t need to wait for the weekly probe — if you suspect a channel issue, post a manual message in the coach UI and watch for delivery errors in /coach/feedback.