PERSONAL PRODUCTIVITY

Protect tomorrow's focus blocks and send a Slack pre-triage digest

Each evening this scans tomorrow's calendar for meetings overlapping your focus blocks, drafts decline-or-keep recommendations.

CategoryPersonal Productivity
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNightly schedule (6pm)
  • ActionFetch tomorrow's eventsGoogle CalendarGoogle Calendar
  • LogicFilter to focus-block conflicts
  • ActionRecommend keep/decline/shortenOpenAI
  • OutputPost pre-triage digest to SlackSlack

What it does

Runs a nightly sweep of the next day's schedule and finds every meeting that collides with your protected focus blocks. Instead of declining silently, it builds a single Slack digest listing each conflict with an AI recommendation (keep, decline, or shorten) and the reasoning, so you make the call in seconds the night before instead of getting ambushed at 9am.

When to use it

You want a human in the loop but hate doing calendar triage in the moment. This gives you a calm, batched review window each evening to defend tomorrow's deep work proactively.

How it works

  1. 1A scheduled trigger fires every evening (e.g. 6pm).
  2. 2The workflow pulls tomorrow's events from Google Calendar and identifies your focus blocks.
  3. 3It filters to only the meetings that overlap those blocks.
  4. 4OpenAI evaluates each conflict and produces a keep/decline/shorten recommendation with a one-line rationale.
  5. 5The flow formats the conflicts into a single digest and posts it to your Slack DM or channel for approval.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect Google CalendarEvents, attendees, availability.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    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.