Set once, runs forever. The Schedule Trigger in n8n is your always-on assistant — it fires reports, syncs and backups exactly when you want them, on UK business time. This guide covers setting up schedules, writing cron expressions, and the practical patterns UK businesses build on top of the Schedule node.
What scheduling is and when to use it • Configuring Schedule Trigger step by step • Cron expressions for advanced schedules • Example scheduled workflows • Managing scheduled tasks • Handling failures gracefully • UK timezone considerations • FAQ
n8n offers three ways to run workflows: manually (click Execute), via webhook (instant reaction to an event in an external system), or via schedule (automatic runs at predetermined times). The Schedule Trigger is the equivalent of a system cron — with a graphical interface, execution history and the ability to build complex workflows without writing code.
When to use a schedule instead of a webhook? Whenever you’re not reacting to a specific event but want to do something regularly, independent of user activity:
Tip: n8n on SmartXHosting runs on UK infrastructure, so scheduled tasks run on UK-localised timezone by default. No timezone confusion across BST/GMT transitions.
Scheduling is also useful for syncing data between systems. If one system doesn’t support webhooks, you can check hourly for new records and import them into the second system. Less elegant than webhook but fully automatic and reliable — and for many uses, an hourly delay is perfectly acceptable.
For more complex schedules (09:00 and 17:00 on weekdays but not weekends), pick Custom in Trigger Interval and enter a cron expression.
Format: minute hour day-of-month month day-of-week
UK examples:
0 9,17 * * 1-5 — 09:00 and 17:00, Monday to Friday*/5 * * * * — every 5 minutes0 8 * * 1 — 08:00 every Monday0 2 * * 0 — 02:00 every Sunday0 9 1 * * — 09:00 on the first of each month30 8 * * 1-5 — 08:30 weekdaysUse crontab.guru to preview and test expressions before entering them in n8n. It shows plain-English interpretation of any cron expression.
Workflow runs daily at 07:30. n8n sends a GET request to the WooCommerce API with date parameters (today’s date), pulling all orders from the last 24 hours. A Code node calculates total GBP revenue, average order value, number of new customers. A Gmail node formats a tidy HTML report and emails it to the finance manager. The whole process takes n8n about 15 seconds — the manager sees the report as they sit down at their desk.
Schedule set for Sunday at 02:00 BST. n8n calls a mysqldump or pg_dump via SSH or a remote endpoint, downloads the backup file and uploads it to AWS S3 or Google Drive via HTTP Request. It also sends an email confirmation with file size and timestamp. Backups older than 30 days are deleted automatically via a companion cleanup workflow.
First of the month at 08:00. Workflow pulls the list of active subscriptions from the database, generates invoices via the Xero, FreeAgent or QuickBooks API, emails them to customers and marks them as “sent” in the CRM. Hundreds of VAT-compliant invoices automatically within minutes — no bookkeeper time required.
Cron */5 * * * * runs the workflow every 5 minutes, 24/7. n8n sends GET to your UK site, checks the response is 200 OK and the response time is below 3 seconds. If not — immediate Slack alert plus Twilio SMS to the on-call engineer. When the site returns to normal, an automatic all-clear message goes out.
HMRC publishes monthly exchange rates. Cron set for the first of each month at 10:00 pulls the new rates from the HMRC API and updates your Google Sheet used for VAT calculations. One less manual task per month for UK exporters.
Cron 07:30 Mon-Fri pulls weather data for UK cities where you have site visits planned that day, formats a team briefing and posts to Slack. Helpful for trades, engineering teams, couriers.
n8n logs every execution — scheduled and manual. Go to Executions in the left panel to see all runs with timestamp, status (Success, Error, Running) and duration. Click a specific execution to see exactly what data flowed through each node — invaluable for debugging.
Filter history by workflow name, status or date range. If a workflow runs every 5 minutes, the list fills quickly — in n8n settings you can limit retained executions (e.g. last 100) or auto-purge older records.
To pause scheduled runs without deleting the workflow, toggle Active off. The workflow stays saved with all settings but won’t trigger automatically. Toggle back on to resume.
Naming convention for schedules: use prefixes like [CRON] Daily sales report or [MONITOR] UK uptime check. Makes the workflow list scannable once you have dozens of them.
Scheduled workflows fail sometimes — an API is down, network blip, unexpected data. Handle robustly:
n8n on SmartXHosting runs on UK time (BST/GMT automatic switch). Schedule times entered are UK local. Example: a schedule set for “09:00 daily” fires at 09:00 British Summer Time in summer and 09:00 GMT in winter — automatically.
If you need a fixed UTC time rather than UK local, use a cron expression with UTC offset in the Schedule Trigger Expression mode (available on some n8n versions). For UK-only businesses, UK local time is almost always what you want.
Daylight Saving transitions: on the Sunday in late March BST starts (+1 hour), and late October BST ends (GMT returns). n8n handles transitions automatically for time-based schedules; no manual adjustment.
Schedule n8n automations on UK time
SmartXHosting n8n runs on UK data centre infrastructure with UK-localised timezone — scheduled reports, backups and monitoring fire on UK business hours automatically.
See n8n hosting plansQ: What happens if a scheduled run overlaps with the previous one?
A: By default n8n starts the new execution regardless. If you want to prevent overlapping runs, use the Workflow Settings › Run Workflow Simultaneously setting. For critical schedules, add logic to skip if a previous execution is still running.
Q: Can I run a schedule only on working days?
A: Yes — cron 0 9 * * 1-5 (Mon-Fri at 09:00) covers weekdays. For UK bank holiday exclusion, add an IF node at the start that checks against a list of UK bank holidays and exits early if today is one.
Q: My schedule says it fired but nothing happened on the storefront.
A: Check the Executions page for the run. Success/Error status plus data preview tells you whether the run completed and what happened at each node.
Q: Can I run a workflow on the last day of each month?
A: Cron 0 23 L * * (where L means last day). Check n8n cron version supports it; if not, schedule for 28th and add logic to check if today is actually the last day.
Q: Will my schedules keep running if I’m away?
A: Yes — n8n runs 24/7 on your SmartXHosting instance, independent of whether you’re logged in.
Q: What happens during server maintenance?
A: SmartXHosting announces maintenance windows in advance. Scheduled runs during the window are skipped; they don’t queue up. For critical schedules, coordinate with support to reschedule maintenance or design workflows to be idempotent.
Q: Can I test a schedule without waiting for the scheduled time?
A: Yes — click Execute Workflow on the canvas to run manually. The workflow behaves as if the schedule had fired.
Q: How many concurrent schedules can n8n handle?
A: Dozens comfortably on a standard SmartXHosting plan. For hundreds of concurrent schedules or sub-second precision, a scaled deployment is needed — contact support for options.