live at the edge · cloudflare pages functions

Know who you’re talking to.

A small, fast Telegram bot that returns the IDs and basic metadata you need for groups, channels, and bot development—without keeping a user database.

Deploy your bot ↓ Explore commands

01 no database 02 webhook-ready 03 token stays server-side

U@your_username/id

⌁User Info BotYOUR TELEGRAM IDSYour user ID: 123456789
Current chat ID: -1001234567890
Message ID: 42

▌

webhook latency42ms

4focused commands

0stored user records

24/7edge availability

HTTPSTelegram webhook

COMMAND MAP / 01

Small surface area.
Useful answers.

Designed for the moments when a numeric ID is the missing piece. Add the bot to a chat, send a command, and get a clean HTML response.

/idmost used

Returns your user ID, current chat ID, and the message ID in one compact response.

Your user ID: 123456789

/useridentity

Shows the sender name, username, language, premium status, and bot status.

Username: @your_username

◫

/chatinfocontext

Shows the current chat title, type, public username, and chat ID.

Type: supergroup

/helpguide

Displays the available commands and the bot’s privacy promise.

No database. No tracking.

DEPLOYMENT / 02

From repository
to response.

The repo is built for Cloudflare Pages Functions. Static files serve the guide, while /api/telegram receives Telegram updates securely at the edge.

Deploy the repository

Connect user-info-bot to Cloudflare Pages, or run the Wrangler command from the README.

Add three secrets

Set TELEGRAM_BOT_TOKEN, TELEGRAM_WEBHOOK_SECRET, and ADMIN_SETUP_KEY in Pages.

Register the webhook

Call the protected setup endpoint once your pages.dev URL is live.

Terminal

# register the default webhook
curl -X POST https://YOUR_PROJECT.pages.dev/api/setup \
  -H 'Authorization: Bearer YOUR_ADMIN_SETUP_KEY'

✓ Your bot token is never placed in the frontend.

⌁

BUILT FOR THE EDGE

Fast where Telegram is.

Cloudflare Pages Functions turns the webhook into a short-lived serverless handler. No VM to patch, no polling loop to keep alive, and no user profile database to maintain.

check health endpoint ↗