Scheduled (cron) trigger
The Scheduled (cron) trigger runs a workflow on a recurring time with nobody starting it. Perfect for reports, reminders and repeating tasks.
Watch this step in the video · Scheduled and incoming webhook
The Scheduled (cron) trigger runs a workflow on a recurring time, with nobody having to start it. It's the foundation for daily reports, periodic reminders, re-engagement campaigns, and anything that should repeat "every Monday at 9" or "on the 1st of each month".
Unlike triggers such as Message received, the scheduled trigger does not carry a conversation or a contact with it: it fires on its own, by the clock. So any node that sends a message needs you to tell it explicitly who to write to.
Requirements
- Available on all plans (from Lite), with a monthly quota of workflow runs based on your plan.
- Permission to manage Workflows in your workspace.
Steps
- Go to Settings → Workflows and click Create workflow (or edit an existing one).
- On the canvas, click Add trigger.
- Pick Scheduled (cron) from the list of system triggers.
- In Cron expression type the 5 standard fields
min hour day month weekday. Examples:0 9 * * 1→ every Monday at 9:00.0 8 * * *→ every day at 8:00.*/15 * * * *→ every 15 minutes.0 9 1 * *→ the 1st of each month at 9:00.
- Add your action nodes. Since there is no source conversation, in a Send message node set the recipient (for example, a broadcast to a segment, or a heads-up to the Team). You can use the
{{$scheduled.execution_time}}and{{$scheduled.iteration}}variables in the text. - Activate the workflow with the toggle at the top.
Verify it
Omnifox checks scheduled workflows every minute, so at the next match with your cron it will fire by itself. To skip the wait, use the Test button in the editor and open the Executions history: there you'll see the date, the status, and the nodes that ran.
If it doesn't work
- It never fires: confirm the workflow is Active and the cron expression is valid (5 fields). Check the Cron generated helper under the field.
- Wrong time: the cron runs in your workspace time zone; adjust the values if your operation lives in another zone.
- No message goes out: remember this trigger has no contact. A Send message node without an explicit recipient has nobody to write to.
Tip: avoid overly frequent expressions (like
* * * * *) if the flow does heavy work; every minute can pile up executions. Start with once a day and tune from there.
Tip: a workflow allows only one trigger. If you need the same process at two different times, create another scheduled workflow that calls this one with a Call workflow node.
Related articles
Related articles
-
Build your first workflow
Omnifox workflows automate your operation: a trigger starts the automation and action nodes do the work. Build a welcome message in minutes.
-
Workflow triggers catalog
Learn which events can start a workflow automatically in Omnifox.
-
Workflows complete guide
Workflows in depth, in 54 chapters: triggers, nodes, variables, testing, history, templates, import and export, with every setting explained and a real workflow end to end.
-
Action nodes available in workflows
Discover the actions a workflow can run automatically.
-
Conditions and branching (if/then) in a workflow
Make your flows take decisions and follow different paths based on each contact data.