CRON / scheduled trigger
A time-based trigger that fires an automation at fixed intervals every morning at 7 AM, every Monday, the 1st of each month. CRON syntax defines the schedule. Used for reports, digests, and maintenance tasks.
Expert insight
Scheduled workflows have a failure mode webhook-triggered ones don't: nobody notices when they silently stop firing. A workflow triggered by a real event fails loudly when the event doesn't produce the expected result, but a CRON job that stops running just produces silence, no report shows up, no digest gets sent, and often nobody checks until a client asks where last week's report went. Scheduled workflows need their own separate monitoring, a check that confirms the job actually ran, not just that it works when tested manually.
How PURIST uses this
This concept is built into every automation we deploy.
When PURIST builds your automation, CRON / scheduled trigger is not an optional consideration it is part of the production standard. Our workflows are tested against edge cases, monitored 24/7, and built to handle what happens when things don't go as expected.
Every client workflow we deploy in the Core concepts category is designed with this principle in mind from day one not added as an afterthought.
Complexity level
Requires some familiarity with automation concepts.
Related terms
See it in action
Want CRON / 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 →More in Core concepts
Keep exploring