Schedule Trigger
Run procedures automatically on a cron schedule.
Overview
The Schedule trigger runs your procedure automatically at a specified interval using a cron expression. Use it for recurring workflows — daily reconciliation jobs, weekly reports, nightly data syncs, or any time-based automation.
Setup
- Add a Schedule trigger to your procedure.
- Enter a cron expression and select a timezone.
- Save the trigger — the first run will occur at the next matching time.
Configuration
| Field | Description |
|---|---|
| Cron | A standard 5-field cron expression |
| Timezone | The timezone for the schedule (e.g. America/New_York, Europe/London, UTC) |
Cron Syntax
┌───────── minute (0–59)
│ ┌───────── hour (0–23)
│ │ ┌───────── day of month (1–31)
│ │ │ ┌───────── month (1–12)
│ │ │ │ ┌───────── day of week (0–7, 0 and 7 are Sunday)
│ │ │ │ │
* * * * *Examples
| Expression | Description |
|---|---|
0 9 * * 1-5 | Every weekday at 9:00am |
0 18 * * 1-5 | Every weekday at 6:00pm |
*/15 * * * * | Every 15 minutes |
0 * * * * | Every hour on the hour |
0 0 * * * | Every day at midnight |
0 0 1 * * | First day of every month at midnight |
0 9 * * 1 | Every Monday at 9:00am |
30 8 1,15 * * | 8:30am on the 1st and 15th of every month |
Payload
Scheduled runs receive no trigger payload — the trigger input is an empty object {}. Design your procedure to operate without trigger-supplied data, or use Tool Call nodes to fetch the data it needs from integrations at runtime.
Timezone Handling
The cron expression is evaluated in the configured timezone. Rapidfolio handles daylight saving time transitions automatically — if a scheduled time falls in a DST gap, the run is skipped for that occurrence and resumes at the next valid time.
Use UTC for jobs that must run at exact intervals regardless of local time. Use a named timezone (e.g. America/New_York) when the schedule should align with business hours in a specific location.
Concurrent Runs
If a scheduled run is still executing when the next scheduled time arrives, Rapidfolio starts a new run regardless. There is no built-in concurrency lock on scheduled triggers. If your procedure must not run concurrently with itself, add a guard in your procedure logic (e.g. a Tool Call that checks a mutex in your system before proceeding).
Example Use Cases
- Run a nightly reconciliation of transaction records against your bank feed.
- Send a weekly summary report to your finance team every Monday at 9:00am.
- Poll an external API for pending items every 15 minutes and process any new ones.
- Run end-of-day KYC re-checks on flagged accounts at midnight.