mirror of https://github.com/tiennm99/claude-status-webhook.git synced 2026-04-17 15:20:37 +00:00

Files

tiennm99 e8b30743d3 refactor: remove cron, use KV metadata, extract shared crypto util

- Remove cron status polling (statuspage notifies via email on webhook failure)
- Store subscriber types/components as KV metadata for O(1) filtering
- Extract timingSafeEqual to shared crypto-utils.js (was duplicated)
- Change /migrate route from GET to POST (prevent CSRF/prefetch)
- Preserve existing subscriber preferences on /start re-subscribe
- Remove dead getAllSubscribers export
- Update docs to reflect changes

2026-04-09 08:58:52 +07:00

3.3 KiB

Raw Blame History

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Project

Telegram bot that forwards status.claude.com (Atlassian Statuspage) webhook notifications to subscribed users. Hosted on Cloudflare Workers.

Commands

npm run dev — Start local dev server (wrangler dev, emulates KV + Queues locally)
npm run deploy — Deploy to Cloudflare Workers
npx wrangler deploy --dry-run — Verify build without deploying
node scripts/setup-bot.js — One-time: register bot commands + set Telegram webhook (requires BOT_TOKEN and WORKER_URL env vars)

No test framework configured yet. No linter configured.

Secrets (set via `wrangler secret put`)

BOT_TOKEN — Telegram bot token
WEBHOOK_SECRET — Secret token in Statuspage webhook URL path

Architecture

Cloudflare Workers with two entry points exported from src/index.js:

fetch — Hono.js HTTP handler (routes below)
queue — CF Queues consumer for fan-out message delivery

Routes

Method	Path	Handler	Purpose
GET	`/`	inline	Health check
POST	`/webhook/telegram`	`bot-commands.js`	grammY `webhookCallback("cloudflare-mod")`
POST	`/webhook/status/:secret`	`statuspage-webhook.js`	Receives Statuspage webhooks (URL secret)
POST	`/migrate/:secret`	inline	One-time KV migration (remove after use)

Data Flow

Statuspage → Worker: Webhook POST → verify URL secret (timing-safe via crypto-utils.js) → parse incident/component event → filter subscribers by type + component → sendBatch to CF Queue
Queue → Telegram: Consumer processes batches of 30 → sendMessage via telegram-api.js helper → auto-removes blocked subscribers (403/400), retries on 429
User → Bot: Telegram webhook → grammY handles /help, /start, /stop, /status, /subscribe, /history, /uptime commands → reads/writes KV

KV Storage

Per-subscriber keys (no read-modify-write races):

sub:{chatId} → { types: ["incident", "component"], components: [] }
sub:{chatId}:{threadId} → { types: ["incident"], components: ["API"] }

kv-store.js handles key building/parsing with kv.list({ prefix: "sub:" }) pagination. Subscriber type/component data is stored as KV metadata so getSubscribersByType() uses only list() (O(1)) instead of individual get() calls. threadId can be 0 (General topic), so null checks use != null.

Component-Specific Subscriptions

Subscribers can filter to specific components via /subscribe component <name>. Empty components array = all components (default). Filtering applies to webhook notifications.

Supergroup Topic Support

Bot stores message_thread_id from the topic where /start was sent. Notifications and queue consumer include message_thread_id in sendMessage payload to target the correct topic.

Key Dependencies

hono — HTTP routing framework
grammy — Telegram Bot API framework (webhook mode for CF Workers)
wrangler — CF Workers CLI (dev/deploy)

CF Bindings (wrangler.jsonc)

claude_status — KV namespace
claude-status — Queue producer/consumer (batch size 30, max retries 3)

3.3 KiB Raw Blame History