go-schedule
Continue to this section of the documentation index.Continue to this section of the documentation index.Continue to this section of the documentation index.Continue to this section of the documentation index.Continue to this section of the documentation index.

Open-source workload automation

Put your workflows
on schedule.

From the first scheduled script to connected, event-driven workflows. Write when it should run. See what happened. Keep work moving.

Get startedDownload the latest release

Windows, Linux and macOS CLI, desktop and API

The daily reporting workflow 09:00
↳
Collect the numbers

Weekdays at 09:00

Success
On completion
↳
Build the report

Run after collection succeeds

Success
On completion
↳
Deliver the result

Notify your team through a webhook

Delivered

An example of schedules, completion chains and notifications working together.

Say when.
Or bring your cron.

Readable schedules and supported cron share one scheduling engine. Choose a timezone, review the next runs, and control what happens when work overlaps or a date is missed.

Explore scheduling syntax
gosched
# Schedule a weekday report
gosched task add weekday-report \
  --command /usr/local/bin/report.sh \
  --schedule "weekdays at 09:00" \
  --tz America/New_York

# Prefer cron? Use "0 9 * * 1-5".
gosched runs --task <task-id>
The CLI reports the interpreted schedule and upcoming runs.

More ways to start.
One place to understand.

Use go-schedule for recurring operations, incoming files, build hooks and dependent jobs. Keep the execution history and the next step within reach.

Time and events, connected

Run on readable schedules, cron, daemon startup, file changes, external triggers or task completion. Group related tasks and connect their outcomes.

Explore commands

A control center for the work

Author tasks, inspect the calendar, follow activity and manage explicitly enrolled remote daemons from the desktop. The daemon keeps scheduling when the window closes.

Meet the desktop

Automation you can build on

Use the CLI, JSON API or optional MCP access. Inspect permissions and audit records, move portable definitions and connect your existing tools.

Read the API reference

A serious place in your automation stack.

See how go-schedule compares with established scheduling and workflow platforms, where it fits today, and what comes next.

Compare capabilities

Your scripts already do the work.
Give them a schedule.

Install go-schedule

Run locally. Connect other daemons when you need them.