Creating schedules requires Business, Team, or Enterprise. Existing schedules keep running if you downgrade, but you can’t create new ones.
Create a scheduled workflow
1
Describe the task and timing
In the editor’s chat, say what to do, which records to include, who receives the result, and when. Include the timezone.
Every day at 9am UTC, email the operations team a summary of tasks that are overdue and still open. Include the task name, owner, and due date.You can also open Workflows → Schedules → Create scheduled task and enter your request there.
2
Review and test
Open Workflows → Schedules. Select Edit schedule on the row to check its timing, timezone, and end policy.Use Run now to test the workflow with the schedule’s saved inputs. It runs the current editor version, so you can test before publishing. Check the result in History.
3
Publish to activate
Select Publish. A schedule marked Not published won’t run automatically yet. After publishing, check its Next run time.
Run now performs real actions, such as changing records or sending emails. Check the saved inputs and recipients before testing.
Edit the timing
Choose Recurring for repeated work or One-time for a single future run. Use Edit with AI to describe a change in plain language, or adjust the fields yourself.
Example: a daily report at 9am UTC. Review the timezone and end policy before saving.
- Run every: Set how often it repeats.
- At times: Choose the time, or add multiple times.
- Timezone: Check which timezone the schedule follows.
- End policy: Keep it running, end on a date, or stop after a set number of runs.
Create user triggered schedules
Ask Zite to add a way for people to schedule work from your published app. For example:Add a Set reminder button to each client request. Let the signed-in user choose a date and time, then email them a reminder with the request title.These schedules appear with an Added by user label in Schedules. Use this approach when each person or record needs a different reminder time.
Manage scheduled workflows
For schedules built into the app, publish after editing, pausing, enabling, or removing them. Changes to schedules added by users take effect without republishing.
Check run history
Select the workflow name, then open History. Use Triggered by, Status, and Time range to find the run, then open it to see what happened. If an expected run is missing, check:- Publication: Is it marked Not published or Unpublished changes?
- Timing: Are the timezone and next run correct?
- Status: Is it paused, or has its end date or run count been reached?