Skip to main content
Give a workflow a schedule field and it fires on that cadence as an additional trigger, so the workflow stays callable from your app too.

Inline schedule

Email comes from the app’s email integration and exists once the app’s zite.config.json has an email entry under integrationSettings. See Integrations & secrets. The schedule is a structured object (recurring or one-time), not a cron string. See Schedules for every field. Always include an IANA timezone.

Rules

  • context.user is null on scheduled fires. Don’t depend on a signed-in user. (Also null on anonymous request fires, so it’s not a reliable “this is a schedule” signal.)
  • Set authenticated: true unless the workflow is meant to be public. A scheduled workflow stays callable by URL, so without it anyone can trigger the work.
  • Scheduled fires skip inputSchema parsing, so schema defaults are not filled in. Read optional fields as input.x ?? fallback.
  • One schedule per workflow. For two cadences, create two workflows that share helper code.
  • Never simulate cadence in code. The schedule field is the only source of truth, so no setInterval/setTimeout or if (week % 2) skip-checks; serverless runs don’t keep timers alive.

Let end users set the schedule

For runtime, end-user-driven cadence (a “remind me every…” setting), use the ZiteSchedules runtime API from zitejs/schedules inside a workflow:
endpointId is not typechecked, so a typo compiles and fails at fire time. Nothing validates inputs against the target’s inputSchema either: make them match yourself, and have the target read optional fields with a fallback. See Schedules for add / list / update / remove.
Scheduled jobs are part of the Business plan.