Every team has the same tasks that run on a clock. Send a morning briefing at 9am. Pull last week's sales data every Monday. Sync the CRM to the knowledge base at midnight. Check SLA status every 15 minutes during business hours. Someone set up these tasks manually once, and now someone else manually runs them — or worse, they just don't run at all.
AACFlow schedule triggers let teams automate any time-based workflow using cron expressions and full timezone support — from daily AI-powered digests and weekly reports to nightly data syncs and real-time SLA monitoring — without writing a single line of code.
AACFlow's schedule trigger changes this. You define when a workflow runs — once, hourly, daily, weekly, on a custom cron pattern — pick a timezone, and walk away. The workflow handles itself.
What Is a Schedule Trigger in AACFlow?
A schedule trigger is an entry point for a workflow that fires automatically based on time. Instead of a user clicking "Run" or an external webhook arriving, the AACFlow scheduler watches the clock and starts the workflow when the configured time comes.
Under the hood, each scheduled workflow is stored in the workflowSchedule table with four key fields: cronExpression (the schedule pattern), timezone (e.g., America/New_York), lastRunAt (when it last fired), and (when it will fire next). The flag lets you pause and resume a schedule without deleting it.
