Cron Trigger

A cron trigger runs your workflow automatically on a recurring schedule.

Setup

1. Add a Cron Trigger node to your canvas
2. Click the node to open settings and configure the schedule in the Parameters pane
3. Add a Sample Payload if downstream nodes need seeded data for testing
4. Click Activate in the editor toolbar

Schedule options

The schedule is stored as a standard 5-field cron expression.

Sample payload

Cron triggers can emit optional JSON seed data. Top-level object fields are available directly, such as {cron.symbol}. If you paste an array or primitive, the editor stores it wrapped as { "body": <value> } and you access it via {cron.body}.

The settings Input pane previews the sample payload while you edit it. If you rerun a cron execution from the editor's executions panel, Solaris AI Flow fires the cron trigger using its current configuration.

Output

Every cron fire emits at minimum:

{
  "triggeredAt": "2026-05-14T10:00:00.000Z",
  "source": "cron"
}

With a Sample Payload such as { "watchlist": ["SOL", "BONK"] }, the trigger output becomes:

{
  "watchlist": ["SOL", "BONK"],
  "triggeredAt": "2026-05-14T10:00:00.000Z",
  "source": "cron"
}

Downstream nodes reference fields with the trigger response name (default cron): {cron.watchlist}, {cron.triggeredAt}. The base fields (triggeredAt, source) always win on key collision.

Day-of-week mapping

For weekly schedules, dayOfWeek follows the standard cron convention: 0 = Sunday, 1 = Monday, ..., 6 = Saturday.

Enabling and disabling

Toggle the workflow from:

• The editor toolbar (Activate / Active)
• The mobile actions menu (Activate Schedule / Deactivate Schedule)
• The updateSchedule action on the workflow

When disabled, the cron stops firing but the configuration is preserved.

Plan restrictions

If you downgrade from Pro to Free with an hourly cron active, it's automatically disabled with a deactivation reason shown in the editor.

Timezone

Cron schedules run in UTC. Configure the hour/minute relative to UTC.

Next steps

• Executions - what happens when a cron fires
• Plans and Limits - trigger quotas by plan