Triggers
A trigger is what starts an automation. It answers one question: when should this run? There are two families of triggers — ones that fire when something happens in your workspace, and ones that fire on a schedule.
Event triggers — “when something happens”
Section titled “Event triggers — “when something happens””Event triggers watch your workspace and fire the moment a specific kind of thing occurs.
| Trigger | Fires when… |
|---|---|
| Task Created | A new task is created. |
| Task Updated | An existing task changes (for example, its status or assignee). |
| Comment Added | Someone comments on a task. |
| Database Entry Created | A new row is added to a database. |
Filters — only run when it matters
Section titled “Filters — only run when it matters”Most of the time you don’t want to react to every event — just the ones that matter. Filters let you add conditions, and the automation only runs when they match.
For example, on a Task Updated trigger you might add filters so the flow runs only when:
- the priority becomes High, and
- the task is in the “Customer Escalations” project.
You can combine several conditions with AND/OR logic. With no filters at all, the automation runs for every occurrence of that event.
Schedule triggers — “at a certain time”
Section titled “Schedule triggers — “at a certain time””Schedule triggers run a flow on the clock, no event required. They’re perfect for reports, reminders, and routine cleanup.
| Schedule | Runs… |
|---|---|
| Once | A single time, at a specific date and time. |
| Daily | Every day at a chosen time. |
| Weekly | On chosen days of the week, at a chosen time. |
| Monthly | On chosen dates of the month, at a chosen time. |
| Interval | Every N minutes or hours. |
All schedules respect your configured timezone, so “9:00 AM daily” means 9:00 AM where you are.
Putting it together
Section titled “Putting it together”A trigger is only half of an automation — pair it with a flow to decide what actually happens. See Automations to wire the two together.