Build a recurring Dots workflow
Design a schedule that produces a useful change report.
Choose the trigger
Use a fixed schedule when the timing matters. Supply day, time, time zone and end date. For event-triggered work, ask the dot to confirm whether the connected source supports that event and what it configured.
Keep a baseline
The first run establishes current state. Later runs should compare against the last completed run and classify added, changed, resolved and removed items. Use stable source links as identifiers whenever possible.
Design the quiet case
Specify what should happen when there is no material change. For a personal watch, a stored check timestamp can be enough; for a weekly report, a short unchanged line may be useful. Match the behavior to the destination.
Confirm and maintain
Ask the dot to confirm the schedule, scope and destination. Inspect scheduled tasks when you change a responsibility. Pausing the main conversation does not necessarily stop delegated tasks or schedules; manage those entries directly.