Event id: schedule.daily
The everyday cadence trigger. Use it when the flow should sweep a set of records rather than react to one change.
When it fires
Once every day, at the hour you set. The hour is interpreted in each recipient’s own time zone, so an 8am daily flow reaches someone in London at 8am London time and someone in New York at 8am New York time.
What the flow receives
- Recipient — The person this run is for, so the flow can scope what it reads to them
- Run date — The date the run is for, which the flow can use in filters and in the text it writes
- Time zone — The recipient’s time zone
A schedule trigger carries no deal or meeting. The flow’s first step decides what to look at, usually a List records or Count and group records step with filters.
Who it runs for
This depends on the flow’s scope, set when you build it:
- Personal — Runs once a day for you
- Company — Runs once a day for every active member of your workspace, each with their own records
A company-wide daily flow with a per-person view produces one run and one output per person, not one shared output.
Good uses
- A morning digest of the day’s meetings, open commitments, and anything that moved overnight
- A daily hygiene sweep that flags deals missing a close date or a next step
- A stalled-deal check that lists deals with no activity for a set number of days
- An end-of-day summary of what changed across the pipeline
Things to know
- Set the hour for when the output is useful, not when the data is ready. A morning digest at 7am beats one at midnight.
- The flow has to pick its own records. Start with a List records step that filters to the recipient’s deals, then narrow from there.
- A daily flow over a wide record set runs for everyone every day. Keep the filters tight or the output stops being read.
- Turning the flow off stops future runs. It does not remove anything already produced.
If the flow is really about one event happening, an event trigger is better. Use a schedule when the value is in the sweep, not in the timing.
