Cron consultants

Q: What does the Cron node do in n8n?

The Cron node (Schedule Trigger) automatically starts a workflow at specified times or intervals. You define when it should fire, for example every 15 minutes, daily at 7am AEST, or on the first Monday of each month, and n8n handles execution automatically. The workflow runs on schedule without any manual intervention or external trigger.

Q: Can a workflow have both a Cron trigger and a Webhook trigger?

Yes. An n8n workflow can have multiple trigger nodes, and each acts as an independent entry point. You might have a Cron node that runs the workflow every morning for a daily sync, plus a Webhook node that allows the same workflow to be triggered on-demand when someone needs an immediate refresh. Only one trigger fires per execution.

Q: How do I test a Cron-triggered workflow without waiting for the schedule?

During development, you can test the workflow using the manual trigger (Start node or Execute Workflow button) without waiting for the Cron schedule to fire. The rest of the workflow runs exactly the same way regardless of which trigger started it. Once you've confirmed everything works, activate the workflow and the Cron node will take over triggering on schedule.

We can help you automate your business with Cron and hundreds of other systems to improve efficiency and productivity. Get in touch if you’d like to discuss implementing Cron.

Get in touch

Book a call

About Cron

The Cron node (now called Schedule Trigger in newer n8n versions) triggers workflows on a time-based schedule. You configure it to fire at specific intervals (every 5 minutes, hourly, daily at 9am, weekly on Mondays, monthly on the 1st), and n8n automatically executes the workflow at those times. No manual triggering or external event is required.

Scheduled execution is essential for automations that need to run on a recurring basis: pulling daily reports from an API, syncing data between systems every hour, sending weekly summary emails, running nightly data cleanup scripts, or checking for new records at regular intervals. The Cron node handles all of these timing patterns.

The node uses standard cron expression syntax, giving you precise control over execution timing. You can set it to run at specific minutes, hours, days of the week, days of the month, and months. For simpler requirements, n8n also provides a visual interface where you select the interval without writing cron expressions directly.

At Osher, the Cron node is the backbone of maintenance and reporting workflows we build for clients. Scheduled data syncs, automated report generation, and periodic health checks all rely on it. Our BOM weather data pipeline used scheduled triggers to pull fresh weather data at defined intervals. We use Cron-triggered workflows across data processing and RPA projects wherever tasks need to happen on a predictable schedule.

If your business has recurring tasks that run on a timer, talk to our n8n team about automating them with scheduled workflows.

Cron FAQs

Frequently Asked Questions

Common questions about how Cron consultants can help with integration and implementation

What does the Cron node do in n8n?

What is a cron expression and how do I write one?

A cron expression is a string of five or six fields that define a time schedule: minute, hour, day of month, month, and day of week. For example, ‘0 9 * * 1’ means ‘at 9:00am every Monday.’ In n8n, you can either write cron expressions directly or use the visual interval selector, which lets you pick common patterns like ‘every hour’ or ‘daily at a specific time’ without writing the expression yourself.

What timezone does the Cron node use?

The Cron node uses the timezone configured in your n8n instance settings. For Australian clients, this is typically set to AEST or AEDT. It’s important to verify the timezone setting before deploying scheduled workflows, especially if your n8n instance runs on a server in a different timezone to your business operations. You can also set the timezone per workflow in newer n8n versions.

Can a workflow have both a Cron trigger and a Webhook trigger?

What happens if a scheduled workflow takes longer to run than the interval between triggers?

If a Cron-triggered workflow is still running when the next scheduled execution time arrives, n8n starts a new execution in parallel. This can cause issues if the workflow modifies shared resources (like a database table or file). For long-running workflows, consider setting a longer interval, adding execution locking logic, or checking for running instances at the start of the workflow.

How do I test a Cron-triggered workflow without waiting for the schedule?

How it works

We work hand-in-hand with you to implement Cron

As Cron consultants we work with you hand in hand build more efficient and effective operations. Here’s how we will work with you to automate your business and integrate Cron with integrate and automate 800+ tools.

Step 1

Process Audit

We review your recurring business processes and their current scheduling methods (manual timers, calendar reminders, cron jobs on servers, or team members running tasks from memory). For each process, we document how often it needs to run, what time window it should execute in, and what dependencies it has on other systems or processes.

Step 2

Identify Automation Opportunities

We identify recurring tasks that are good candidates for scheduled automation: daily data syncs, hourly inventory checks, weekly report generation, monthly billing runs, and similar time-based processes. Each candidate is assessed for scheduling requirements, execution duration, and any timing conflicts with other scheduled tasks or system maintenance windows.

Step 3

Design Workflows

We design the workflow with the Cron node as the entry point, configuring the schedule expression to match your business requirements. We also build in safeguards like execution timeout handling, error notifications for failed scheduled runs, and logging so you can verify the workflow executed on schedule and completed successfully.

Step 4

Implementation

We configure the Cron node with the correct schedule expression and timezone, build the downstream processing nodes, and test the full workflow using manual execution. Once tested, we activate the workflow and monitor the first several scheduled executions to confirm the timing is correct and the workflow completes within the expected window.

Step 5

Quality Assurance Review

We verify that the workflow fires at the correct times by checking execution logs over several schedule cycles. We also test edge cases like daylight saving time transitions, what happens on months with different numbers of days (for monthly schedules), and how the workflow behaves if the n8n server restarts during a scheduled execution window.

Step 6

Support and Maintenance

After deployment, we monitor scheduled execution logs for missed runs, failed executions, or timing drift. When your scheduling needs change (different frequency, new time window, additional tasks to run on the same schedule), we update the Cron configuration and verify the new schedule works correctly.

Transform your business with Cron

Unlock hidden efficiencies, reduce errors, and position your business for scalable growth. Contact us to arrange a no-obligation Cron consultation.

Get in touch

Book a call