Menu
Connect a Telegram bot to the Vellum Assistant gateway with automated webhook registration and credential storage
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Read, search, send, and manage messages across Gmail, Outlook, Telegram, and other platforms
An on-demand personal daily briefing โ weather, headlines, the shape of your day, and one thing worth your attention โ in a sharp executive-assistant voice. The general-purpose morning brief; richer work or admin digests compose it as their general layer.
One-time migration of an existing memory-v2 concept corpus into the memory-v3 section-grain "wiki" โ topical articles with a stand-alone lead and queryable sections โ with loss-proof staging, assistant-reviewed authoring, and a retrieval-eval gate before cutover.
Delegate a big or high-stakes job to a fleet of parallel subagents, orchestrated deterministically; runs unattended and reports back
Manage contacts, communication channels, access control, and invite links
Build and edit small, personal visual tools and artifacts โ dashboards, trackers, calculators, data visualizations, charts, simple landing pages, and slide decks the user wants for THEMSELVES. This is the right skill whenever the user asks to "visualize this," "make a chart," or "build an artifact" for their own use, or to edit an app they already built here. Do NOT reach for a ui_show dynamic_page to fake an artifact โ build a real persistent app here. NOT for complex, multi-user, or shippable products โ those go to a real project folder with a coding agent (see Scope below).
| name | telegram-setup |
| description | Connect a Telegram bot to the Vellum Assistant gateway with automated webhook registration and credential storage |
| compatibility | Designed for Vellum personal assistants |
| metadata | {"icon":"assets/icon.svg","emoji":"๐ค","vellum":{"category":"messaging","display-name":"Telegram Setup","activation-hints":["Telegram bot setup, webhook configuration, or BotFather token","User wants to connect Telegram to the assistant"],"avoid-when":["User wants to send/receive Telegram messages (use messaging skill instead)"]}} |
You are helping your user connect a Telegram bot to the Vellum Assistant gateway. Walk through each step below.
| Value | Type | Storage method | Secret? |
|---|---|---|---|
| Bot Token | Credential | assistant credentials prompt | Yes |
| Bot Username | Config | assistant config set telegram.botUsername | No |
| Webhook Secret | Credential | assistant credentials set | Yes |
assistant credentials prompt - never accept it pasted in plaintext chat.Tell the user: "You'll need a Telegram bot token from @BotFather. Open Telegram, message @BotFather, and use /newbot to create one."
Collect the token through the secure credential prompt:
Run (via the bash tool):
assistant credentials prompt --service telegram --field bot_token \
--label "Telegram Bot Token" \
--placeholder "123456:ABC-DEF1234ghIkl-zyx57W2v1u123ew11" \
--description "Enter the bot token you received from @BotFather"
BOT_TOKEN=$(assistant credentials reveal --service telegram --field bot_token)
GETME_RESPONSE=$(curl -sf "https://api.telegram.org/bot${BOT_TOKEN}/getMe")
BOT_USERNAME=$(echo "$GETME_RESPONSE" | jq -r '.result.username')
assistant config set telegram.botUsername "$BOT_USERNAME"
If the curl call fails, the token is invalid - ask the user to re-enter (repeat Step 1).
Use the unified webhooks CLI to get a callback URL. This handles both platform-managed and self-hosted assistants automatically:
CALLBACK_URL=$(assistant webhooks register telegram --source "$BOT_USERNAME")
If the command fails because no public base URL is configured (self-hosted only), load the public-ingress skill to walk the user through setting one up, then retry the command.
Check to see if one already exists:
assistant credentials inspect --service telegram --field webhook_secret
If not, generate and set one:
assistant credentials set --service telegram --field webhook_secret "$(uuidgen)"
After registering the platform route (or obtaining a public ingress URL), you must also tell Telegram to send updates to that URL. The gateway may do this automatically on restart, but its safest to also register explicitly:
BOT_TOKEN=$(assistant credentials reveal --service telegram --field bot_token)
WEBHOOK_SECRET=$(assistant credentials reveal --service telegram --field webhook_secret)
curl -s "https://api.telegram.org/bot${BOT_TOKEN}/setWebhook?url=${CALLBACK_URL}&secret_token=${WEBHOOK_SECRET}"
Confirm Telegram has the correct URL registered:
WEBHOOK_INFO=$(curl -sf "https://api.telegram.org/bot${BOT_TOKEN}/getWebhookInfo")
echo "$WEBHOOK_INFO" | jq .
REGISTERED_URL=$(echo "$WEBHOOK_INFO" | jq -r '.result.url')
Compare REGISTERED_URL to CALLBACK_URL. If they don't match, the webhook was not set correctly. Retry the setWebhook call. Do not report success until getWebhookInfo confirms the correct URL and shows no last_error_message.
BOT_TOKEN=$(assistant credentials reveal --service telegram --field bot_token)
curl -sf -X POST "https://api.telegram.org/bot${BOT_TOKEN}/setMyCommands" \
-H "Content-Type: application/json" \
-d '{"commands":[{"command":"new","description":"Start a new conversation"},{"command":"help","description":"Show available commands"}]}'
Non-critical - warn on failure but don't block setup.
Now let's test the connection by verifying the user can receive your messages. This confirms everything works and links the user's Telegram identity for future message delivery.
Load the guardian-verify-setup skill:
skill_load with skill: "guardian-verify-setup".If the user explicitly wants to skip this step, proceed to Step 6, but let them know they can always verify later by saying "verify me on Telegram".
Summarize:
To disconnect Telegram:
assistant credentials delete --service telegram --field bot_token
assistant credentials delete --service telegram --field webhook_secret
assistant config set telegram.botUsername ""