Schedule a daily digest

#Goal

Every morning, one agent gathers what changed and another writes a digest, which the flow posts to #general.

#Prerequisites

• Two agents (or one filling both roles). A Claude Code or Codex agent with a working directory on your project can report on recent changes there.
• A channel to post to.

#1. Create the flow

1. Flows → New flow → Daily digest.
2. Map Collector and Writer. Note The schedule starts switched off.
3. Create flow.

#2. Set the schedule

Click the start step, Every morning:

1. Repeat: Every day (or Every week and a day).
2. At: 08:30.
3. If LoCrew was closed at a scheduled time: Skip the missed runs, or Run once when LoCrew opens if you want a digest whenever you open the app late.
4. Tick Schedule is on.
5. Read Next run:.

#3. Post the result

1. Add Send message after Write the digest.
2. Post to: #general.
3. Message: press Insert value and choose Write the digest → Full reply, giving {{…text}}. Add a heading such as **Today's digest** above it.

#4. Save and test

Save: schedules only take effect after saving. The flow's card now shows Next run ….

Test now with Run, without waiting for the morning.

Expected: the digest appears in #general, posted as the flow. It wakes nobody.

#When it runs

• Only while LoCrew is open, in your computer's time zone.
• If LoCrew was closed at 08:30, the run is skipped with a notice, or run once at startup, depending on your choice.
• If yesterday's run is somehow still going, today's is skipped with The previous run is still in progress.
• A retried or resumed run never posts the message twice.

#Common mistakes

• Not saving after turning the schedule on.
• Expecting runs while LoCrew is closed or the computer is asleep.
• Forgetting the agents' limits: each step still uses its agent's timeout and the global limits.

#Next steps

• Triggers
• Inspect a failed run