Inbox Digest Cron
Seed inbox messages in Redis or memory, then a Cron-style Route Handler summarizes a digest (AI or deterministic).
Run this experiment yourself
Demos are not embedded on this site. Deploy a standalone copy on Vercel or run the experiment app locally.
Local development
cd apps/experiments/inbox-digest-cron pnpm install pnpm dev
Then open http://localhost:3010.
This is an experimental demo. Use it as a starting point for your own projects.
Inbox Digest Cron seeds sample messages into Redis (or process memory), then a Cron-style Route Handler builds a digest. With AI configured it summarizes; otherwise it deterministically joins subjects/bodies. Cron invocations check CRON_SECRET.
Features
- Seed inbox – sample partner/ops messages.
- Cron digest –
vercel.jsonschedule hits/api/digest. - AI or deterministic – never invents messages when AI is missing.
- Redis or memory – honest UI notes when Redis is absent.
Server Reference
POST /api/seed
Seeds sample messages.
GET /api/digest?run=1
Runs a digest (authorize with Bearer CRON_SECRET in production). Without run=1, returns the last digest.
POST /api/digest
Cron-friendly run (same auth rules).
| Status | Cause |
|---|---|
401 | Missing/invalid CRON_SECRET |
Implementation Details
Seed
Write message array to Redis key or module memory.
Digest
generateText when AI is available; else deterministicDigest.
Use Cases
- Learn Cron + Redis composition.
- Prototype inbox digests before production queues.
Limitations
- Demo-scale message caps.
- Deterministic mode is a join, not a model summary.
Use in your project
Copy handlers from apps/experiments/inbox-digest-cron/.
Deployment
Local Development
cd apps/experiments/inbox-digest-cron
pnpm install
pnpm devConfiguration
| Variable | Required | Purpose |
|---|---|---|
CRON_SECRET | Prod | Authorize cron |
AI_GATEWAY_API_KEY | No | AI digest |
UPSTASH_REDIS_REST_URL / TOKEN | No | Durable messages |
Vercel / Next.js Features Used
- Vercel Cron
- Upstash Redis
- AI SDK
generateText - Route Handlers