Back to Integrations
Trigger

Schedule

The Schedule Trigger allows your workflows to run completely hands-free based on time. Whether you need a task to execute every 15 minutes, once a day at midnight, or on a complex cron expression, the Schedule node is the master clock for your automated operations.

Schedule
Core / Trigger
⚠️

What can you do with Schedule?

Fixed Intervals

Easily set up simple repeating schedules like "Every 1 hour" or "Every 30 days" without any complicated configuration to keep regular data synchronization tasks flowing.

Advanced Cron Expressions

For ultimate precision, use standard 5-part cron expressions (e.g., '0 0 * * 1-5' for weekdays at midnight) to dictate exactly when your nodes should spring into action with minute-level accuracy.

Timezone Awareness

Run scheduled operations consistently in the customized timezone of your choice, ensuring your automated reports, data backups, or customer emails happen exactly when expected by your local team.

Detailed Usage & Configuration

The Schedule node transforms your automation canvas into a powerful background cron-job agent. It acts as the heartbeat of your system, initiating executions precisely when dictated.

1. Configuration Modes

The node is highly configurable and adapts to both technical operators and standard users:

  • Standard Intervals: Select units like seconds, minutes, hours. For example, syncing Shopify product data every 15 minutes.
  • Daily/Weekly Aggregations: Set specific hours, like "Every Monday at 9:00 AM" to dispatch a weekly performance report natively.
  • Advanced CRON: Power users can input classic 5-part cron syntax (e.g., 0 12 * * 1-5) to construct intricately complex temporal conditions.

2. How Data is Passed

Because the run is triggered entirely by the passing of time, it does not naturally contain "external form data" like a Webhook. However, the node injects precise timestamp variables into the payload pipeline (e.g. $json.timestamp), which can be mapped downstream to find relational database rows corresponding exactly to the moment the trigger fired.

🛡️ Platform Requirement: This node only actively triggers in production environments when the workflow is explicitly in the Published state. The nLink architecture strictly requires at least one active Trigger Node (like Schedule or Webhook) present on the canvas before it allows a workflow to be successfully published. This ensures the compiled graph is functionally reachable.