ops ✦ 81~30 min setupintermediate

Telegram webhook bridge (no poll turns)

@siraustin walks BotFather token → webhook (Cloudflare Tunnel optional) so a Grok Bot answers Telegram DMs without burning turns on polling. Idle stays cheap. Distinct from the YouTube-era telegram-inbox-bridge page on this site.

1

Copy the prompt below.

2

Paste it into Grok — open your Grok Bot and send it as your first message.

3

Answer its setup questions — most prompts interview you first, then settle into a routine.

The prompt

Prompt
Adapt this outline. Do not treat it as a finished prompt. Never ask me to paste the BotFather token into a public gist or this chat.

Walk me from a Telegram BotFather token to a Grok Bot that answers Telegram DMs over a webhook bridge.
Prefer webhook over polling so idle does not consume Grok Bot turns.
Optional: Cloudflare Tunnel if I lack a public HTTPS endpoint.
Store the token in the secure field you name.
Share: https://x.ai/bot/3EyXrWLkGfi4SG-dMy427
Start: confirm whether I already have a BotFather bot.

How it's set up

@siraustin: hook Grok Bot to Telegram without consuming tokens/turns on polling; optional Cloudflare Tunnel webhook. Share https://x.ai/bot/3EyXrWLkGfi4SG-dMy427 (live).

Distinct from telegram-inbox-bridge on this site (YouTube general bridge): this page teaches the no-poll webhook path.

  1. Create a BotFather bot; keep the token private.
  2. Follow the share's webhook steps.
  3. Smoke-test with a DM before sharing the bot handle widely.
  4. Matching shared bot (live): /bots/telegram-bridge-share/.

Why it works

Polling bridges quietly burn allowance. Webhook idle is the ops lesson.

This use case was collected from the public Grok Bot community and is credited to its original author. Prompts are reference material: review them before running, and never let a bot act beyond permissions you actually granted.