telegram-native-8787
$
npx mdskill add vercel-labs/vercel-openclaw/telegram-native-8787Diagnose Telegram webhook failures and execute native recovery workflows.
- Resolves webhook validation errors and sandbox listener failures.
- Integrates Vercel logs, OpenClaw providers, and drain-channel workflows.
- Cross-references project targeting and delivery IDs for root cause.
- Delivers sanitized configuration and post-accept reply visibility.
SKILL.md
.github/skills/telegram-native-8787View on GitHub ↗
--- name: telegram-native-8787 description: "Telegram channel specialist workflow: debug /api/channels/telegram/webhook, native port 8787 /telegram-webhook, webhookSecret, boot cleanup, and post-accept reply visibility." --- # Telegram Native 8787 Use after `channel-debug-core` for Telegram issues. ## Files - `src/app/api/channels/telegram/webhook/route.ts` - `src/server/channels/telegram/**` - `src/server/workflows/channels/drain-channel-workflow.ts` - `src/server/openclaw/config.ts` - `src/server/admin/why-not-ready.ts` - `src/app/api/channels/summary/route.ts` ## Runtime Path ```text Telegram update -> /api/channels/telegram/webhook -> secret header validation -> dedup -> fast path to sandbox port 8787 /telegram-webhook OR workflow -> local/public native handler probe -> OpenClaw Telegram provider -> Telegram user-visible reply ``` ## Parallel Lane Inputs To Consume Before proposing a Telegram fix, consume: - Vercel/app logs lane: accepted webhook, planner event, fast-path result, workflow handoff, requestId/deliveryId/update_id, and project targeting proof. - Sandbox runtime lane: actual sandboxId, port 8787 listener, local/public `/telegram-webhook` probe, sanitized config has `channels.telegram`, webhookSecret presence without value. - Workflow lane: `drainChannelWorkflow` run state and whether 8787 not-listening/ECONNREFUSED triggered reconciliation, with verified project targeting when `.vercel/project.json` differs from the incident target. - Prior-fix comparison: webhookSecret flow, suspicious_empty_200, stale 8787 URL refresh, boot-message cleanup. ## Special Checks - Port 8787 is not port 3000. - Native handler registered evidence is local/public probe behavior, especially local 401 on invalid secret. - Fast, empty 200 is suspicious; do not call it accepted. - `lastRestoreMetrics.telegramListenerReady` is evidence, not the whole truth. - `webhookSecret` must flow through config build, restore assets, dynamic resume files, and config hash. - Accepted forward does not prove a visible Telegram reply. - Boot message send/update/delete behavior is user-visible evidence.
More from vercel-labs/vercel-openclaw
- admin-ui-debugAdmin UI and operator surface debugging for vercel-openclaw: command shell design, admin actions, request core, status panels, launch verification UI, channel readiness UI, and local read-only production-data workflows. Use when the root admin UI, controls, visual state, or operator copy is wrong.
- auth-store-debugAuth and store debugging for vercel-openclaw: admin-secret mode, Sign in with Vercel, session cookies, CSRF, LOCAL_READ_ONLY, Redis vs memory store, keyspace namespacing, and metadata shape migrations. Use when login, route authorization, Redis persistence, or metadata state is suspect.
- channel-debug-coreChannel webhook triage for vercel-openclaw Slack/Telegram/Discord/WhatsApp issues: prove deployment state, collect admin readiness endpoints, build evidence-first handoff before fixes.
- channel-forward-parityWebhook route parity audit for channel delivery changes: ensure terminal paths log, record lastForward, classify failures, and refresh stale sandbox port URLs.
- cron-watchdog-debugCron and watchdog debugging for vercel-openclaw: Vercel Cron auth, persisted OpenClaw jobs, cron wake keys, token refresh, restore oracle, hot spare, and watchdog reports. Use when scheduled OpenClaw jobs fail to wake or run, watchdog status is wrong, cron persistence is suspect, or /api/cron/watchdog behavior changes.
- discord-deliveryDiscord channel specialist workflow: debug interaction webhooks, Ed25519 signatures, deferred replies, workflow forwarding to /discord-webhook, integration reconcile, and token expiry.
- firewall-ai-gateway-debugFirewall and Vercel AI Gateway debugging for vercel-openclaw: network policy allowlists, OIDC token refresh, AI Gateway transform rules, firewall learning/enforcement, and sandbox.update networkPolicy calls. Use when model calls, egress, token refresh, or firewall policy application fails.
- gateway-proxy-debugGateway and proxy debugging for vercel-openclaw: /gateway routing, HTML injection, WebSocket rewrite, gateway-token handoff, waiting page, status heartbeat, sandbox port URL cache, and proxy auth. Use when the OpenClaw UI, WebSockets, gateway proxying, or waiting-page flow breaks.
- lat-md>-
- launch-verify-debugLaunch verification and remote smoke debugging for vercel-openclaw: preflight, queue ping, ensureRunning, chatCompletions, wakeFromSleep, restorePrepared, channelReadiness, NDJSON progress, and vclaw create readiness. Use when launch verification, vclaw create validation, or remote smoke checks fail.