Skip to content
New: a free website for your business, live in 48 to 72 hoursWorkflow automation on n8n and Claude, built for your businessFixed price, agreed before we start · Live in 5 to 10 business days30-day money-back guarantee on every planProfessional firms · Agencies · E-commerceYou own every workflow, in your own n8nClaude API: your data is not used for trainingHuman approval on every sensitive stepFree automation audit, no obligation
PURIST
30 days
Money-back window
14 h/wk
Modeled time saved
99.97%
Uptime SLA
< 7 days
Deploy time
PURIST AI
Claude Opus 4.7 · n8n v1.71 · <80ms
What type of business are you running? I'll show you exactly which processes we'd automate first and your estimated ROI.
Powered by n8n + Claude Opus 4.7 Get my free automation plan →
Core concepts
Beginner

Scheduled trigger

An automation that fires at a defined time rather than in response to an event. Examples: "every weekday at 7am, compile overnight orders"; "every 1st of the month, generate invoices"; "every Friday at 4pm, send the weekly KPI digest".

Expert insight

A scheduled trigger set in the workflow platform's server timezone, not the business's local timezone, causes a "runs at 7am" automation to actually fire at 2am or noon local time depending on where the server is hosted, a subtle misconfiguration that's easy to miss until someone notices the timing is off.

In a real workflow

A report workflow runs every Monday at 8 am.

Common mistakes

  • Time zone confusion.
  • Overlapping runs when one takes longer than the interval.

Complexity level

Beginner

Anyone can understand this no technical background needed.

Quick facts

Category Core concepts
Level
Beginner

Browse the full glossary

← All 325 terms

See it in action

Want Scheduled trigger built into your automation?

Book a free audit and we'll show you exactly how this applies to your business.

Get my free automation plan →