Skip to main content

​
What It Does

  • Triggers workflows at set times — hourly, daily, or custom intervals.
  • Adds a UTC timestamp to every workflow run for logging and audit trails.
  • Provides a structured JSON of UTC-based time details (year, month, day, hour, minute, second, timezone).
  • Powers time-based automations like daily reports, SLA checks, and pipeline snapshots.

​
Output

The Scheduler Node outputs a dataset with one column:
ColumnDescription
dataJSON string containing current UTC time details

​
Example JSON:

{
  "timestamp": "2025-07-25T14:07:00.087Z",
  "Day of week": "Friday",
  "Year": "2025",
  "Month": "July",
  "Day of month": "25",
  "Hour": "14",
  "Minute": "07",
  "Second": "00",
  "Timezone": "UTC"
}
If your table already has a data column, the system auto-renames it (e.g., data_1).

​
How It Works

  1. Reads your schedule configuration.
  2. At the scheduled time, triggers the workflow.
  3. Captures the current UTC time at that exact moment.
  4. Formats time details into JSON (timestamp, date, time, timezone).
  5. Outputs the dataset with the data column for downstream use.

​
🚀 Example Use Cases & Prompts

Use CaseSetup Example
Daily Pipeline ReportTrigger every morning at 8am; timestamp report
SLA MonitoringRun every hour; log cases missing SLA deadlines
Weekly SnapshotsTrigger Fridays at 5pm; export pipeline snapshot
Activity LoggingAdd timestamps to audit trails automatically

​
✨ Pro Tips

Use clear column names. Rename data → execution_time downstream to make logs and reports easier to read.
Adjust for your local timezone. Since output is always in UTC, apply conversion downstream if your team works in a different timezone.

​
⚠️ Important Considerations

The Scheduler always captures the execution time in UTC. It does not generate “future” times.
If your reporting or SLAs are based on local business hours, you’ll need to convert from UTC downstream.

​
🛠 Troubleshooting & Gotchas

SymptomLikely CauseQuick Fix
Workflow doesn’t triggerSchedule misconfiguredDouble-check your schedule format
Time doesn’t match local TZScheduler outputs UTCAdd conversion logic downstream
Column renamed to data_1Naming conflict in datasetRename output column for clarity

​
📝 FAQ

✅ Yes — set daily or hourly schedules, or use cron expressions for precision.
No — output is always UTC. Convert downstream if you need local time.
Yes, this is a listening node and all listening nodes take 1 Credit.

​
💰 Pricing

ActionCredit Cost
Workflow trigger event1 credit each
The Scheduler Node consumes 1 credit per scheduled trigger (e.g., hourly, daily).
Any downstream processing may add additional credits depending on nodes used.

⏰ Put the Scheduler Node at the top of your workflow to run tasks automatically—hourly, daily, or on any schedule you set. 🚀