What are Schedules?
Schedules automate Flows to run at specific times or intervals, enabling batch processing, monitoring, and recurring workflows without manual intervention.
Schedules in practice
A growth lead at a B2B sales intelligence startup needed to identify companies hiring for VP of Sales roles—prime prospects for their product. Manually checking job boards took hours and often meant missing opportunities to competitors who reached out first.
She built a Flow that scrapes LinkedIn and startup job boards for new VP Sales postings, enriches each company with funding data and tech stack info, scores them based on ideal customer criteria, and generates personalized outreach messages referencing their specific hiring needs.
She set the Flow to run daily at 6 AM, targeting a Record Type called "lead-sources" that contains URLs for job board searches. Each morning, the Flow processes fresh postings overnight, populates her CRM with qualified leads, and queues outreach emails—all before her team's standup.
After two weeks, she checked the run history and noticed some job boards were updating at different times. She split the schedule into two: one at 6 AM for boards that update overnight, another at 2 PM for boards that post during business hours. She also adjusted her scoring criteria in the Flow after seeing that Series A companies converted better than seed-stage.
The result: her pipeline went from 12 qualified leads per week (found manually) to 45 per week on autopilot. Response rates improved by 30% because her team reached prospects within hours of job postings going live, not days later.
Test your Flow manually before scheduling it to ensure it handles inputs correctly and completes successfully.
Creating a schedule
Click Schedules in the sidebar under the Manage section, then click Create Schedule.
Configure the following required settings:
Flow
Select the Flow you want to run. The dropdown lists all Flows in your workspace.
Target
Choose what Records the Flow will process:
Record Type: Run the Flow against all Records of a specific type
Record IDs: Run against specific Records. Enter comma-separated Record IDs (the IDs shown in your Records table).
Timing
Set when the schedule runs:
One-time: Select a specific date and time for a single execution.
Recurring: Choose from these frequency options:
Every few minutes: 1, 5, 10, 15, or 30 minutes
Every hour: Specify which minute of the hour (e.g., :15 for 15 minutes past)
Daily: Set the hour and minute for daily execution
Weekly: Choose day of week and time
Monthly: Choose day of month and time
Time zone
Your schedule uses your current time zone (detected from your browser) unless you change it when creating or editing. For recurring schedules, this ensures execution times remain consistent regardless of server location (e.g., \"Daily at 9 AM\" always runs at 9 AM in that time zone).
Click Create to save the schedule.
Your plan may limit the number of active schedules or restrict certain frequencies. If you hit a limit, upgrade your plan or pause existing schedules.
Managing schedules
The Schedules page shows all your schedules and their run history.
Edit a schedule
Click any schedule row to open it. Modify the Flow, target, or timing settings, then click Update.
Pause or resume
Click the pause icon to stop future executions while keeping the configuration. Click the play icon to resume. Paused schedules show a \"Paused\" badge.
Run now
Click the Run now button (refresh icon in the schedule row) to queue an immediate execution outside the regular schedule.
Delete a schedule
Click the trash icon and confirm deletion. This stops all future executions but preserves run history.
Viewing run history
Below the schedules list, Run History shows all past executions with Flow name, status, progress, and timestamps. Click any run to view detailed results.
If a scheduled execution fails, the schedule continues running on its normal cadence. Check the run history or execution logs to diagnose issues.
Best practices
Start with manual testing: Run your Flow manually with test Records before scheduling
Choose appropriate frequency: Don't over-schedule—use daily if hourly isn't necessary
Monitor early runs: Check the first few scheduled executions in run history to catch configuration issues
Use Record Types for batches: When processing multiple Records, target a Record Type rather than listing individual IDs
Next steps
Automating batch processing for scheduled batch jobs
Creating and editing flows to build Flows for scheduling
Creating and managing records to set up Record Types and Records for scheduled processing
Viewing execution logs to monitor scheduled runs