Skip to main content
A schedule trigger fires your script on a recurring basis without any manual action. You define when it should run — daily, weekly, monthly, or on a custom cadence — and Script.it creates a new session and runs the script each time the schedule fires. Schedule triggers are well-suited for reports, digests, data syncs, and any routine task that belongs on a fixed cadence.

​
Setting up a schedule trigger

1

Open the Triggers tab

Open the script you want to schedule. Click the Triggers tab, then click Add Trigger.
2

Name the trigger and choose Schedule

Enter a name for the trigger — something descriptive like “Daily sales report”. In the Trigger Type dropdown, select Schedule.
3

Choose a frequency

Use the How often? dropdown to pick a preset or write a custom cron expression:
  • Every 30 minutes — runs twice an hour
  • Every hour — runs at the start of each hour
  • Every few hours — choose an interval of 2, 3, 4, 6, 8, or 12 hours
  • Every day at… — runs once a day at the time you select
  • Every weekday at… — runs Monday through Friday at the time you select
  • Every week on… — runs once a week on the day and time you select
  • Every month on… — runs once a month on the day (1–28) and time you select
  • Advanced (custom cron) — enter a cron expression directly
The UI shows a plain-English summary of your schedule as you build it (for example, “At 9:00 AM, every day”).
The minimum allowed interval is every 30 minutes. Schedules that would fire more frequently than that are not accepted.
4

Set the timezone

Use the Timezone picker to choose the timezone your schedule should be interpreted in. By default, this is set to your browser’s timezone. If you share a trigger with a team member in another timezone, make sure the timezone is set explicitly so the schedule fires when you expect.
5

Choose the script

Pick the script to run, and fill in any inputs it needs.
6

Create the trigger

Click Create Trigger. The trigger activates immediately and will fire at its next scheduled time.
You can skip the form entirely and describe the schedule in chat: “Run this every weekday morning at 8 AM.” The agent sets it up for you.

​
Cron expression format

When you select Advanced (custom cron), you write a standard five-field cron expression:
Each field accepts a specific set of values:

​
Common examples

All cron expressions are evaluated in the timezone you selected. 0 9 * * 1 means Monday at 9:00 AM in your chosen timezone, not UTC — unless you explicitly choose UTC as the timezone.

​
What happens when a schedule fires

When a scheduled trigger fires, Script.it runs your script. The run appears in your session history like any other, and if the script produces output files they’re available there. If a scheduled run fails — because the script has an error, say — the trigger stays active and tries again at the next scheduled time. If it fails five times in a row, Script.it pauses it and lets you know. See Managing triggers.

​
Turning a schedule off

Use the switch on the trigger in your script to stop it firing without losing its settings, and the same switch to start it again. Deleting a trigger removes it for everyone in the workspace who had enabled it — see Managing triggers before you delete a schedule on a shared script.