Runtype
Schedules

What are Schedules?

Schedules let you run your Flows automatically at a specific time or on a recurring cadence. Instead of starting a Flow manually each time, you create a Schedule and Runtype runs it for you.

Test your Flow manually before scheduling it so you know it handles your inputs correctly and completes successfully.

Schedules in practice

A growth lead at a B2B sales intelligence startup needed to identify companies hiring for VP of Sales roles. Manually checking job boards took hours and meant missing opportunities to faster-moving competitors.

She built a Flow that scrapes job boards for new VP of Sales postings, enriches each company with funding data, scores it against ideal customer criteria, and generates personalized outreach messages.

She set the Flow to run daily at 6 AM and targeted 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 before her team’s standup.

After reviewing the run history, she noticed some boards updated at different times. She split the work into two Schedules: one at 6 AM for boards that update overnight and another at 2 PM for boards that post during business hours.

The result was a larger pipeline on autopilot and faster outreach while new opportunities were still fresh.

Creating a Schedule

To create a Schedule, go to Schedules in the sidebar under Manage, then click Create schedule.

Configure these settings:

Flow

Select the Flow you want to run. The list includes the Flows in your workspace.

Target

Choose which Records the Flow should process:

  • Record Type runs the Flow against all Records of a specific type. This works well for batch processing because new Records of that type are included automatically.

  • Record IDs runs the Flow against specific Records. Enter the IDs as a comma-separated list when you only want to process a known set of Records.

Timing

Choose whether the Schedule runs once or on a recurring cadence.

One-time runs the Flow at one specific date and time.

Recurring runs the Flow on a repeating schedule. Runtype supports recurring timing options such as frequent intervals, hourly, daily, weekly, and monthly schedules.

Time zone

Your Schedule starts with your browser’s current time zone, but you can change it while creating or editing the Schedule. For recurring Schedules, this keeps the execution time consistent in that selected time zone.

Click Create to save the Schedule.

Start with a less frequent cadence, then increase it after you confirm the Flow is behaving as expected.

Managing Schedules

The Schedules page shows your existing Schedules, their next run, current status, and a separate Run History section below.

Edit a Schedule

Click a Schedule row to open it, update the Flow, target, or timing settings, then click Update.

Pause or resume

Use the pause action to stop future executions without removing the configuration. Use the resume action to turn it back on. Paused Schedules show a Paused status badge.

Run now

Use Run now to queue an immediate execution outside the normal cadence. This is useful when you want to test an updated Flow without waiting for the next scheduled run.

Delete a Schedule

Use the delete action to stop all future executions. Your past run history stays available for review.

Viewing run history

Below the Schedules list, Run History shows past executions with the Flow, status, progress, and timestamps. Open a run to review the results and see how processing completed. If you need more detail about what happened during a run, check What are Logs?.

Watch your first few scheduled runs closely. If something fails, the Schedule still keeps its normal cadence, so check What are Logs? when you need more detail.

Best practices

  • Start with manual testing. Run your Flow with test Records before you automate it.

  • Choose the right cadence. Match the Schedule to how often your data changes.

  • Use Record Types for batches. This keeps future Records in scope without editing the Schedule. If you need to create or organize those Records first, see Creating and managing records.

  • Monitor early runs. Review the first few executions to catch configuration issues quickly.

  • Split Schedules when needed. If sources update at different times, create separate Schedules instead of one catch-all run.

Next steps

Was this helpful?