PERSONAL PRODUCTIVITY

Team Meeting-Free Window Enforcer

Reads every team member's calendar, finds a shared open window for a recurring no-meeting focus period, and books a busy hold on each calendar.

CategoryPersonal Productivity
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule fires before target week
  • ActionPull free/busy for each team memberGoogle CalendarGoogle Calendar
  • LogicIntersect availability, pick best shared slot
  • ActionCreate No-Meetings holds on all calendarsGoogle CalendarGoogle Calendar
  • OutputPost protected vs. conflict summary to SlackSlack

What it does

This workflow finds and protects a shared focus window across a whole team. It reads each member's free/busy data, identifies the recurring slot where the most people are free, places a busy "No Meetings" hold on every calendar, and reports who still has a conflict so the team can resolve it together.

When to use it

Use it when a team agrees in principle to a weekly meeting-free block but no one wants to manually coordinate everyone's calendar. It turns a fuzzy agreement into enforced holds and a clean conflict list.

How it works

  1. 1A weekly schedule fires before the target week.
  2. 2The workflow pulls free/busy data for each team member from Google Calendar.
  3. 3A decision step intersects availability to pick the slot with the highest free-member count.
  4. 4It creates a busy focus-hold event on every member's calendar for that slot.
  5. 5It posts a summary to Slack listing who is protected and who has an unresolved conflict to negotiate.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect Google CalendarEvents, attendees, availability.
  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.