At a glance
Outcome
Daily personalized developer digest in OpenClaw
Time
About 5-10 minutes
Needs
OpenClaw + ClawHub + Snapbyte API key
Best for
OpenClaw cron automation
Step-by-step tutorial
Complete each step in order. You can copy every snippet.
1) Install ClawHub CLI
bashnpm i -g clawhub2) Install the Snapbyte OpenClaw skill
bashclawhub install snapbyte-digest-api3) Configure
SNAPBYTE_API_KEYAdd this in
~/.openclaw/openclaw.json.json5{ skills: { entries: { "snapbyte-digest-api": { enabled: true, apiKey: "snap-your-api-key" } } } }4) Verify skill output
Run from the installed skill directory.
bashcd ~/.openclaw/skills/snapbyte-digest-api python3 scripts/snapbyte_digest.py latest python3 scripts/snapbyte_digest.py history --configuration-id 12 --page 1 --limit 10Expected result: markdown output for latest digest and paginated history.
5) Schedule daily digests with OpenClaw cron
Use isolated cron for exact-time delivery.
Cron vs heartbeat: use cron (isolated) when you need exact send time. Use heartbeat for flexible periodic checks.
bashopenclaw cron add \ --name "Snapbyte Daily Digest" \ --cron "0 7 * * 1-5" \ --tz "America/Los_Angeles" \ --session isolated \ --message "Use snapbyte-digest-api and send my daily developer digest with top links and one-line why it matters." \ --announce \ --channel lastExpected result: a new cron job ID appears and runs on your configured timezone.
6) Validate scheduled runs
bashopenclaw cron list openclaw cron runs --id <job-id> --limit 50 openclaw cron run <job-id> --dueExpected result: job appears in list and run history includes recent status.
Troubleshooting
- - 401 errors: check
SNAPBYTE_API_KEYin~/.openclaw/openclaw.json. - - Skill not available: confirm install with
clawhub install snapbyte-digest-apiin your active OpenClaw workspace. - - Cron fires at wrong time: verify
--tzand inspect runs withopenclaw cron runs --id <job-id>.
Get API key
Create a Snapbyte account, generate an API key, and connect it to OpenClaw with SNAPBYTE_API_KEY.