Schedule

Run on a fixed interval or at specific times (daily, weekly, monthly, yearly). Publish the workflow to activate the schedule.

Usage and specifics

Choose interval, calendar or cron. The timezone and selected days determine the actual trigger time. Publish to activate scheduling.

Technical type : schedule. Runtime : nodulz.

Guided example

To run processing Monday through Friday at 09:00 Paris time:

1. Choose Calendar mode and Weekly frequency.
2. Select Monday through Friday and add time 09:00.
3. Set the timezone to Europe/Paris instead of keeping UTC if you want local time.
4. Connect the processing steps and test them from the editor.
5. Publish, then check an automatically triggered execution at the expected time.

The corresponding configuration is:

{
  "mode": "calendar",
  "timezone": "Europe/Paris",
  "calendar": {
    "frequency": "weekly",
    "times": ["09:00"],
    "weekdays": [1, 2, 3, 4, 5]
  }
}

Technical weekdays range from 0 (Sunday) to 6 (Saturday). In a custom cron expression, the same weekly rule is 0 9 * * 1-5, evaluated in the selected timezone. For a simple cadence, Interval mode accepts values such as 5m or 1h.

Node output exposes triggeredAt, timezone, mode and scheduling settings. triggeredAt is an ISO timestamp; compare it in the intended timezone rather than reading a raw UTC hour as local time.

Credentials and prerequisites

This node defines no dedicated external credential. Remote sources or execution targets may still need their own access credentials.

See the credentials guide if a remote source or execution target requires access.

Parameters

Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.

Configuration help

interval
Interval

Shorthand (5m, 1h, 1d) or a full cron expression with spaces.

timezone
Timezone

IANA timezone used when evaluating the schedule.

Examples

• Interval 1h → every hour
• Fixed times → Mon–Fri at 09:00
• 0 9 * * 1-5 → weekdays at 09:00

Initial configuration

Initial catalog configuration example, to adapt before running. Keep secrets in credentials.

{
  "mode": "interval",
  "interval": "1h",
  "timezone": "UTC",
  "calendar": {
    "frequency": "daily",
    "times": [
      "09:00"
    ],
    "weekdays": [
      1,
      2,
      3,
      4,
      5
    ],
    "monthDays": [
      1
    ],
    "yearlyDates": [
      "01-01"
    ],
    "cron": "0 9 * * *"
  }
}

Verification

Check manual processing and automatic triggering after publication separately. Verify the day and time using the configured timezone. Publish again after changing the time or timezone. Clicking Execute does not prove the schedule is active.

See also : Expressions and data, Executions, Node catalog.