Scheduling recurring automations
Time-based automations use the schedule trigger. Dailybot evaluates the next run against the org or automation timezone so “every Monday morning” means the same local morning for the anchor you pick.
- Open Automations and create a new workflow or edit an existing one.
- Select Schedule (or Time-based) as the trigger.
- Pick a preset (Daily, Weekly, Monthly) or switch to Custom / cron-style entry if your product surface exposes it.
- Set the clock time and, for weekly schedules, the weekday; for monthly, the day-of-month or “last Friday” style rule your UI offers.
- Choose the timezone: org default, UTC, or a named region. Confirm it matches where the audience works.
- Add conditions if the job should skip holidays or only run during business hours (see Triggers and conditions reference).
- Define actions (for example post digest text, pull report snippet, or call webhook).
- Run Test for the next scheduled slot preview when available; otherwise trigger a one-off test send.
- Activate the automation and verify the first live execution in history.
Weekly digest example: Trigger weekly on Friday 16:00 America/New_York; action posts open blockers from the last seven days to #leads.
Monthly survey example: Trigger monthly on day 1 at 10:00 Europe/Madrid; action sends a link to a Dailybot form and pins instructions in the team channel.
DST changes follow the normal rules of the chosen timezone; if your team spans zones, prefer UTC plus explicit copy in the message, or split into two automations per region.