B
Briefed

Schedule a personal newsletter job with GitHub Actions

3 min read · Last updated November 16, 2026

If you already have a script that builds an issue, a scheduled workflow can run it when your laptop is closed. Decide where its state will survive between runners before you enable recurring mail.

Test the script manually

Add a workflow with workflow_dispatch and run the newsletter builder in preview mode. Check the rendered subject, item count and original links in its preview output, with private addresses and credentials omitted.

Add a scheduled trigger

Put the workflow on the default branch. A cron expression of 17 7 * * 1 means Monday at 07:17 with the default UTC schedule. Scheduled runs can be delayed, so determine the issue window from saved state rather than actual job start time.

Keep the issue key outside the runner

Use a persistent private store for an issue ID, cutoff and sending state. Serialize jobs sharing the same issue, and review provider acceptance after any timeout before replaying that issue.

Trigger section for your existing digest workflow
on:
  workflow_dispatch:
  schedule:
    - cron: '17 7 * * 1'

concurrency:
  group: weekly-reading-digest
  cancel-in-progress: false

Sources

Get a personal email on this topic

Briefed researches public web sources using the description you write below. Edit the example and choose how often your newsletter arrives. See the full DIY vs Briefed comparison for setup and maintenance tradeoffs.

How often?

No credit card. No app to install. Unsubscribe with one click, anytime.

Questions

Why did a manual run work while the scheduled run never started?

Verify the workflow containing schedule is on the default branch and enabled. Check Actions run history before debugging the email provider.

More guides