Overview
The Scheduled Time trigger (also called "Recurring schedule") starts a workflow at defined regular intervals. This is useful for automated tasks that need to run on a schedule.
When It Triggers
At the specified time and frequency
Based on your configured schedule (hourly, daily, weekly, monthly)
Automatically executed by the system
Use Cases
Daily reports and summaries
Weekly analytics
Monthly cleanup tasks
Regular data synchronization
Scheduled maintenance
Automated backups
Periodic notifications
Batch processing
Configuration
This trigger requires configuration of the schedule frequency and timing.
Frequency Options
Hourly
Runs every hour at a specific minute
Example: Every hour at minute 15 (1:15, 2:15, 3:15, etc.)
Configuration:
hourly_minute(0-59)
Daily
Runs once per day at a specific time
Example: Every day at 9:00 AM
Configuration:
time(HH:MM format)
Weekly
Runs on specific days of the week
Example: Every Monday and Friday at 10:00 AM
Configuration:
weekly_days(array of days),time
Monthly
Runs on specific days of the month
Example: 1st and 15th of each month at 8:00 AM
Configuration:
monthly_days(array of day numbers),time
Configuration Fields
frequency(required) - One of:hourly,daily,weekly,monthlytime(required for non-hourly) - Time in HH:MM formathourly_minute(required for hourly) - Minute (0-59)weekly_days(required for weekly) - Array of day namesmonthly_days(required for monthly) - Array of day numbers (1-31)
Available Data
When this trigger fires, it provides time and tenant information.
Context Data Structure
Your Information
tenant.name- Your Organization nametenant.timezone- Your Organization timezone
Time Information
current_date- Current date (YYYY-MM-DD format)current_time- Current time (HH:MM:SS format)timestamp- Unix timestamp
Accessing Context Data
{tenant.name}
{tenant.timezone}
{current_date}
{current_time}
{timestamp}Example Workflows
1. Daily Report
Workflow Steps:
Trigger: Scheduled Time (Daily at 8:00 AM)
Action: Find Bookings (from yesterday)
Action: Loop (for each booking)
Action: Aggregate data
Action: Send Notification (daily summary report)
2. Weekly Analytics
Workflow Steps:
Trigger: Scheduled Time (Weekly on Monday at 9:00 AM)
Action: Find Bookings (last 7 days)
Action: Calculate metrics
Action: Send Webhook (send to analytics dashboard)
4. Hourly Sync
Workflow Steps:
Trigger: Scheduled Time (Hourly at minute 0)
Action: Find Bookings (last hour)
Action: Send Webhook (sync to external system)
5. Business Hours Check
Workflow Steps:
Trigger: Scheduled Time (Daily at 9:00 AM)
Condition: If
{current_date}is weekdayAction (True): Send Notification (start of day checklist)
Testing
When testing this trigger:
Default test data uses current date/time
You can modify test data to simulate different times
Review execution logs to see time context used
Test Data
The trigger provides:
Current organization name and timezone
Current date, time, and timestamp
All values reflect the actual current time
Best Practices
Choose appropriate frequency - Don't schedule too frequently for resource-intensive tasks
Consider timezone - Be aware of tenant timezone settings
Use conditions - Filter by date/time for specific scenarios
Handle errors - Set up failure notifications for scheduled workflows
Monitor performance - Track execution times for scheduled workflows
Avoid conflicts - Don't schedule too many workflows at the same time
Test thoroughly - Verify schedules work as expected before activating
Schedule Examples
Every Hour
Frequency: hourly
Hourly minute: 15
Runs: 1:15, 2:15, 3:15, etc.
Every Day
Frequency: daily
Time: 09:00
Runs: Every day at 9:00 AM
Weekdays Only
Frequency: weekly
Weekly days: ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"]
Time: 08:00
Runs: Weekdays at 8:00 AM
First of Month
Frequency: monthly
Monthly days: [1]
Time: 00:00
Runs: 1st of each month at midnight