Schedule Trigger
A scheduled trigger node in n8n that uses Cron expressions to configure scheduling rules. Its timezone interpretation depends on the runtime environment's default timezone or a workflow-specific setting.
Core Facts
In an n8n workflow, a Schedule trigger node can be used to periodically check data sources and sync them to a knowledge base, with the tutorial configured to trigger every 10 minutes.
The Schedule node runs workflows automatically on a time basis, supporting triggers at a fixed time each day, every hour, or at custom intervals.
Webhook triggers are suitable for scenarios that require real-time response to external events, while scheduled trigger nodes are suitable for scenarios such as batch processing and periodic synchronization.
Timeline (last 90 days)
n8n's Schedule Trigger node allows a workflow to start automatically at preset time intervals without manual intervention.
When n8n exports a workflow JSON, the Schedule Trigger's parameters are saved as a structured rule object rather than a raw cron string.
n8n's Schedule Trigger is not suitable for event-driven scenarios (such as triggering when an email is received or when a Webhook is called); those require the corresponding dedicated trigger nodes.
A scheduled n8n workflow run that fails will not be retried automatically unless an error workflow is configured.
n8n's Schedule Trigger supports trigger interval granularities such as seconds, minutes, hours, days, weeks, and months.
The Schedule Trigger, SMTP sending, and Google Sheets writing mentioned in the article are all built-in n8n nodes.
The Cron expression of a Schedule Trigger itself carries no timezone information, and its interpretation depends on the default timezone of the execution environment.
The timezone of an n8n workflow can be individually modified in the Timezone option in the Settings panel of the workflow menu.
n8n's Cron Trigger provides a graphical wrapper on top of classic cron expressions, and users can choose preset periods or customize time points.
In an n8n workflow, a Schedule trigger node can be used to periodically check data sources and sync them to a knowledge base, with the tutorial configured to trigger every 10 minutes.
2 more timeline events
All Facts (12)
In an n8n workflow, a Schedule trigger node can be used to periodically check data sources and sync them to a knowledge base, with the tutorial configured to trigger every 10 minutes.
65%VerifiedThe Schedule node runs workflows automatically on a time basis, supporting triggers at a fixed time each day, every hour, or at custom intervals.
65%VerifiedWebhook triggers are suitable for scenarios that require real-time response to external events, while scheduled trigger nodes are suitable for scenarios such as batch processing and periodic synchronization.
65%UnverifiedWhen n8n exports a workflow JSON, the Schedule Trigger's parameters are saved as a structured rule object rather than a raw cron string.
50%Unverifiedn8n's Schedule Trigger node allows a workflow to start automatically at preset time intervals without manual intervention.
50%Unverifiedn8n's Schedule Trigger supports trigger interval granularities such as seconds, minutes, hours, days, weeks, and months.
50%UnverifiedA scheduled n8n workflow run that fails will not be retried automatically unless an error workflow is configured.
50%Unverifiedn8n's Schedule Trigger is not suitable for event-driven scenarios (such as triggering when an email is received or when a Webhook is called); those require the corresponding dedicated trigger nodes.
50%UnverifiedThe Schedule Trigger, SMTP sending, and Google Sheets writing mentioned in the article are all built-in n8n nodes.
50%UnverifiedThe timezone of an n8n workflow can be individually modified in the Timezone option in the Settings panel of the workflow menu.
50%UnverifiedThe Cron expression of a Schedule Trigger itself carries no timezone information, and its interpretation depends on the default timezone of the execution environment.
50%Unverifiedn8n's Cron Trigger provides a graphical wrapper on top of classic cron expressions, and users can choose preset periods or customize time points.
50%