claude-code-routine-trigger

GitHub Actions workflow that fires a Claude Code routine four times a day via the /fire API.

Schedule (UTC+7, Asia/Ho_Chi_Minh):

Local time	UTC cron
05:00	0 22 * * *
10:00	0 3 * * *
15:00	0 8 * * *
20:00	0 13 * * *

Manual workflow_dispatch is supported with an optional text input for ad-hoc runs.

Setup

1. Create a routine at https://claude.ai/code/routines (requires a Pro/Max/Team/Enterprise plan with Claude Code on the web enabled).
2. In the routine editor, add an API trigger and generate a token. Copy both the fire URL and the token — the token is shown once.
3. Add two repository secrets (Settings → Secrets and variables → Actions):
   • ROUTINE_FIRE_URL — e.g. https://api.anthropic.com/v1/claude_code/routines/trig_01ABo4hmfydBLFDgRMnKwEKy/fire
   • ROUTINE_FIRE_TOKEN — e.g. sk-ant-oat01-...
4. Enable Actions for the repo. Scheduled runs start on the next matching UTC tick.

Manual run

Actions → Trigger Claude Code Routine → Run workflow. Leave text blank to get a timestamped default, or pass custom context (alert body, log line, etc.).

Request shape

curl -X POST "$ROUTINE_FIRE_URL" \
  -H "Authorization: Bearer $ROUTINE_FIRE_TOKEN" \
  -H "anthropic-version: 2023-06-01" \
  -H "anthropic-beta: experimental-cc-routine-2026-04-01" \
  -H "Content-Type: application/json" \
  -d '{"text": "Scheduled trigger ..."}'

Beta header pinned to experimental-cc-routine-2026-04-01. Two previous dated beta versions keep working while migrating — bump when Anthropic ships a new one.

Notes

• GitHub cron runs can lag 5–15 min under load and are best-effort — acceptable for housekeeping-style routines, not for precise timing.
• Token is scoped to a single routine; a leak can only fire that one routine.
• Each POST creates a new session (no idempotency). Avoid retry loops that would multiply sessions.
• 429 responses include Retry-After; the workflow fails loud rather than retrying silently.

License

MIT