PERSONAL PRODUCTIVITY

End-of-day sweep: send approved drafts and snapshot what's still unhandled

At day's end, reviews everything the triage agent drafted, flags any low-stakes reply still sitting unsent.

CategoryPersonal Productivity
Enginesim
Difficultybeginner
Triggerschedule
Steps4
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerScheduled end-of-day run
  • ActionPull day's Gmail drafts and focus-label messagesGmailGmail
  • LogicSeparate ready drafts, overdue replies, and open deep-work
  • OutputPost end-of-day accountability report to SlackSlack

What it does

This is the closing companion to live triage. At the end of each workday it audits the day's drafts and deferred items: it counts approved drafts still waiting in Gmail, surfaces stale low-stakes replies that should just go out, and snapshots the deep-work focus queue that's still open. The result is one honest Slack report of where the day actually landed instead of a vague sense of being behind.

When to use it

Use it alongside any live triage flow when you want a daily accountability checkpoint. Ideal for operators who want to end the day knowing exactly what's drafted, what's stuck, and what rolls to tomorrow.

How it works

  1. 1A scheduled trigger fires at end of day.
  2. 2The flow pulls the day's Gmail drafts and queued focus-label messages.
  3. 3A logic step separates ready-to-send drafts from still-open deep-work items.
  4. 4It flags low-stakes drafts older than a threshold as overdue to send.
  5. 5It compiles counts and titles for each bucket.
  6. 6A Slack end-of-day report posts drafts pending, overdue replies, and unhandled deep-work items rolling to tomorrow.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GmailRead, draft, send, label.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.