Triggers & Inputs
Schedule Trigger Documentation
Automate your document pipelines on a recurring basis using flexible cron-like scheduling.
Quick Answer: What is the Schedule Trigger Node?
[!NOTE] The Schedule Trigger Node allows you to automate workflows without any external event. You can set the workflow to run every hour, every day, or on specific days of the week. This is ideal for batch processing invoices, generating nightly reports, or syncing spreadsheets.
Core Capabilities
1. Recurring Batch Processing
Use the Schedule Trigger to "Check for new files" every morning at 9:00 AM. Connect it to a Google Drive Node to sweep for new PDFs and process them for OCR.
2. Monitoring & Alerts
Create "Heartbeat" workflows that run every hour to check for system outages or to generate status reports from your database.
3. Report Generation
Schedule a workflow to run at 23:30 every Sunday to aggregate the week's document conversions into a single PDF Summary and email it to your team.
Configuration Guide
| Field | Setting | Example |
|---|---|---|
| Interval | How often to run. | Every Hour |
| Start Date | When to begin the first run. | 2026-05-01 |
| Payload | Static context to inject. | { "type": "weekly_audit" } |
Best Practices
- Avoid Overlap: If your workflow takes 10 minutes to finish, avoid scheduling it more frequently than every 15 minutes to prevent queue buildup.
- Resource Cleanup: Use a Merge Node at the end of scheduled runs to ensure batch logs are consolidated for review.
[!TIP] Need a one-time execution? Use the Manual Trigger Node for testing or ad-hoc runs before committing to a schedule.