Schedule Trigger

The Schedule Trigger starts a workflow on a recurring cron schedule.

Purpose and use: Entry node for recurring scheduled work, such as periodic review or synchronization when enabled and authorized in the target installation.

Configuration: Optional cronExpression literal; editor default is 0 * * * * (hourly). It is a cron expression, not a workflow expression. Legacy cronSchedule and schedule aliases are accepted; missing expression defaults to hourly.

Input/output and routing: No input ports; one output port. The scheduler supplies an occurrence payload. In schema-v2/v3 graphs, the schedule starts from declared entryNodes; connect the trigger’s output to downstream work.

Expressions: The cron field is static. Downstream settings may use workflow expressions on the scheduler payload, but the payload’s exact fields are not a fixed user input contract here.

Errors and effects: Invalid cron or failed graph preflight prevents schedule registration/activation. A durable occurrence claim prevents duplicate execution across workers. The trigger itself is not a write; downstream actions may be. Active state and scheduler readiness are installation-specific.

Example configuration — fields validated against the 1.1.1 node schema; replace the identifiers with your own: {"type":"trigger_schedule","data":{"label":"Schedule Trigger","config":{"cronExpression":"0 * * * *"}}}. Expected result: once the schedule is registered and active, each occurrence emits its input to the graph.