Deployment
Crypto Sentinel runs on GitHub Actions as a scheduled workflow. No server needed. The easiest way to get started is to fork this repo and configure your own secrets and variables.
GitHub Setup
Repository Secrets
Go to Settings → Secrets and variables → Actions → Secrets:
| Secret | Required |
|---|---|
GEMINI_API_KEY | Yes |
RESEND_API_KEY | Yes |
TELEGRAM_BOT_TOKEN | No |
TELEGRAM_CHAT_ID | No |
Repository Variables
Go to Settings → Secrets and variables → Actions → Variables:
| Variable | Example |
|---|---|
WATCH_KEYWORDS | binance,bybit,youhodler |
RECIPIENT_EMAIL | your@email.com |
How It Runs
The workflow (.github/workflows/monitor.yml):
- Checks out the repo
- Sets up Node.js 22 with npm cache
- Restores
cache.jsonfrom GitHub Actions cache - Installs dependencies (
npm ci) - Builds TypeScript (
npm run build) - Runs the sentinel (
node dist/index.js) - Actions cache automatically saves updated
cache.json
Manual Trigger
Go to Actions → Crypto Sentinel → Run workflow in GitHub to trigger a run immediately.
Cache Persistence
Seen articles are tracked in cache.json to avoid re-processing. This file is persisted between runs using actions/cache@v4 — it’s not committed to the repo.
The cache keeps the last 500 article IDs. Old entries are automatically pruned.