Skip to main content
Time-based triggers run automations on a schedule. Execute routine maintenance, dependency updates, and compliance checks automatically—without manual intervention.

​
What are time-based triggers

Time-based triggers use schedules to run automations at specific times or intervals. The automation executes automatically based on your configured schedule. Use time-based triggers for:
  • Routine dependency updates
  • Scheduled security scans
  • Periodic compliance checks
  • Regular documentation updates
  • Nightly builds or tests

​
Configure time-based triggers

When creating an automation with a time-based trigger, configure the target scope and schedule:

​
Target scope

Choose where the automation runs: Target projects:
  1. Select Projects as the target type
  2. Choose one or more projects from the list
  3. The automation runs on all repositories within those projects
Target repositories:
  1. Select Repositories as the target type
  2. Select an environment class for the automation to use
  3. Enter a search query to filter repositories (see Manual Triggers for search examples)
Time-based trigger configuration with target selection

​
Set the schedule

Define when the automation runs using simple schedule options:
  1. Choose the frequency:
    • Hourly - Runs every hour
    • Daily - Runs once per day
    • Weekly - Runs once per week
    • Monthly - Runs once per month
  2. Select the minute when the automation runs (0-59)
  3. For weekly schedules, choose the day of the week
  4. For monthly schedules, choose the day of the month
Schedule configuration interface

​
Schedule examples

​
Hourly schedules

Run automations every hour at a specific minute:
  • Every hour at minute 15 - Runs at 1:15, 2:15, 3:15, etc.
  • Every hour at minute 0 - Runs at 1:00, 2:00, 3:00, etc.
  • Every hour at minute 30 - Runs at 1:30, 2:30, 3:30, etc.

​
Daily schedules

Run automations once per day:
  • Daily at 2:00 AM - Select Daily, minute 0, hour 2
  • Daily at 12:30 PM - Select Daily, minute 30, hour 12
  • Daily at 6:15 PM - Select Daily, minute 15, hour 18

​
Weekly schedules

Run automations on specific days of the week:
  • Every Monday at 9:00 AM - Select Weekly, Monday, minute 0, hour 9
  • Every Friday at 5:00 PM - Select Weekly, Friday, minute 0, hour 17
  • Every Sunday at midnight - Select Weekly, Sunday, minute 0, hour 0

​
Monthly schedules

Run automations on specific days of the month:
  • First day of month at midnight - Select Monthly, day 1, minute 0, hour 0
  • 15th of each month at 3:00 PM - Select Monthly, day 15, minute 0, hour 15
  • Last day of month at 11:59 PM - Select Monthly, day 31, minute 59, hour 23

​
Timezone handling

Schedules run on UTC (Coordinated Universal Time) but display in your local timezone in the UI for convenience. Example:
  • You configure: “Daily at 2 AM” (in your local timezone)
  • The UI shows: “Daily at 2 AM EST” (or your timezone)
  • The automation runs: At 7 AM UTC (if you’re in EST)
When setting schedules, the UI automatically converts your local time to UTC. The automation executes at the correct UTC time regardless of your location.

​
Use cases

​
Weekly dependency updates

Keep dependencies current with automated weekly checks: Configuration:
  • Schedule: Every Monday at 2 AM
  • Target: All repositories
  • Steps: Check for updates, run tests, create pull requests
Result: Fresh dependency updates ready for review every Monday morning.

​
Nightly security scans

Scan for vulnerabilities while your team sleeps: Configuration:
  • Schedule: Daily at 1 AM
  • Target: All repositories
  • Steps: Run security scanner, create issues for findings
Result: Security issues identified and triaged before the workday starts.

​
Monthly compliance reports

Generate compliance reports on a regular schedule: Configuration:
  • Schedule: First day of month at midnight
  • Target: All repositories
  • Steps: Check licenses, verify dependencies, generate report
Result: Compliance status documented automatically every month.

​
Hourly documentation sync

Keep documentation in sync with code changes: Configuration:
  • Schedule: Every hour at minute 15
  • Target: Repositories with “docs” tag
  • Steps: Regenerate docs, check for broken links, commit updates
Result: Documentation stays current throughout the day.

​
Next steps