Skip to main content
A schedule runs a saved workflow on a fixed cadence, with no manual trigger. Use it to keep lists fresh, send recurring digests, or research CRM data again. To create and manage schedules from code, see Workflow Schedules. Pair recurring runs with the Deduplicate with Notebook block so each run saves only new rows. See Building Workflows.

Create a schedule

The workflow must be saved and runnable. Until every block is configured, the Schedules option is disabled.
  1. Open the workflow in the Workflow Editor.
  2. Open the More options menu (⋮) next to Run and select Schedules. You can also click Run and then Schedule, or open schedules from the workflow’s row in the Workflows list. Workflow Editor More options menu with Schedules highlighted
  3. Pick a cadence under Repeats, then set its options.
  4. Optionally expand Advanced options to set a name and timezone.
  5. Click Create schedule. The editor shows when the first run starts.
Custom schedules take a standard 5-field cron expression, minute hour day-of-month month day-of-week: An invalid cron expression or timezone is rejected when you save.

Manage schedules

A workflow can have several schedules. Each one in the list shows its name, cadence, and next run, or Paused when it is paused. Per-schedule actions:
  • Pause or resume the schedule without deleting it.
  • Edit the cadence, name, or timezone, then click Save changes.
  • Delete the schedule. The workflow is not affected.
Schedules belong to the workflow’s team, and their runs count toward the team’s monthly credit limit. A schedule keeps running after its creator leaves, unless an admin pauses it during the removal. Sixtyfour pauses a schedule that runs with an API key when that key is revoked or expires, and every schedule when its team is archived; the list shows why. After you resume a schedule, its runs are attributed to you. Scheduled runs use credits the same way manual runs do. See Credit Costs. New scheduled runs appear in GET /v1/jobs?workflow_id={workflow_id} after a short delay. Use the returned job_id to poll GET /v1/jobs/{job_id} for status and output files.
A scheduled run of a workflow that starts with an Incoming Webhooks block processes the block’s saved sample input every time, and each run uses credits. Without a sample input, every scheduled run fails. To process new rows from your systems, trigger the workflow through the Workflows API instead.

Tips

  • Spread schedules that share a cadence across :00, :15, :30, and :45.
  • Keep the cadence longer than a run takes. Each scheduled time starts a new run even while the previous one is still going. See Overlapping and missed runs.
  • Set the timezone deliberately. A 9:00 AM schedule created from a browser in another timezone runs at 9:00 AM there.