How it works
- A Scheduled Workflow finds tickets via filters.
- It triggers your existing Triggered Workflow for each ticket.
Setup
Create the scheduled workflow
Name it “Scheduled [Triggered Workflow Name]” and set your cadence (daily at 8AM, hourly, one-time via Run Now).
Filter tickets
Add precise filters (e.g., New + Unassigned; Board = Help Desk; Created ≤ 7 days).
Add Trigger Another Workflow
Pick the target Triggered Workflow. Set bypassing of filters depending on whether you want double filtering.
Use cases
Morning dispatch
Dispatch overnight tickets before the day begins.
Apply to existing tickets
Run a new Triggered Workflow against the last 7 days of tickets.
Off-peak batch processing
Run heavy workflows at night to reduce daytime load.
Best practices
Make sure a ticket can leave your filter. The scheduled workflow re-runs its filter on every tick, so any ticket that still matches gets triggered again. If the target is meant to act once, either turn on Run only once per ticket on it, or filter on something the run itself changes (a status, or a custom field the agent writes).The trap is the second option failing quietly: if the agent skips that write - no data to compute a value, a condition not met - the ticket keeps matching and is re-triggered every cycle until you notice. Watch Executions for the same ticket number repeating at your schedule’s interval.A time-bounded filter is the third option: with Created ≤ 7 days, a ticket leaves the filter as it ages, even if nothing writes to it.
