PERSONAL PRODUCTIVITY

Defend a focus block by rebooking the meeting someone scheduled over it

When a teammate books a meeting that collides with a protected focus block, this proposes a new time on a shared free slot, moves the meeting there.

CategoryPersonal Productivity
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew meeting created on calendarGoogle CalendarGoogle Calendar
  • LogicDoes it collide with a protected focus block?
  • ActionFind mutual free slot for all attendeesGoogle CalendarGoogle Calendar
  • ActionReschedule the meeting to the new slotGoogle CalendarGoogle Calendar
  • OutputNotify attendees of the move in SlackSlack

What it does

Instead of just declining, this actively rescues both the meeting and your focus block. When an invite lands on top of a protected hold, it finds a time that works for all required attendees, reschedules the meeting into that slot, and posts a heads-up to the relevant Slack channel so no one is surprised by the move.

When to use it

For team leads who need to keep recurring focus blocks but can't simply reject collaborative meetings outright. Use it when rescheduling is the right answer rather than declining.

How it works

  1. 1A new event on your Google Calendar triggers the flow.
  2. 2The flow checks the invite against your protected focus blocks.
  3. 3A branch exits if there's no conflict; otherwise it continues to defend the block.
  4. 4It queries free/busy for all required attendees and selects the earliest mutual opening.
  5. 5It updates the meeting to the new time in Google Calendar.
  6. 6It posts a short message to Slack tagging attendees with the old and new times.
  7. 7The output records that the block was protected and the meeting relocated.

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.