PERSONAL PRODUCTIVITY

Auto-Decline Meetings That Collide With Focus Blocks

Watches your calendar for new meeting invites that overlap a protected focus block.

CategoryPersonal Productivity
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew or updated calendar eventGoogle CalendarGoogle Calendar
  • LogicDetect overlap with a protected focus block
  • LogicScore invite priority (organizer, size, keywords)
  • ActionAuto-decline low-priority invite with a noteGoogle CalendarGoogle Calendar
  • OutputDM high-priority conflicts to me in SlackSlack

What it does

This workflow guards the deep-work blocks you put on your calendar. When a new meeting invite lands on top of a focus block, it scores the meeting by priority signals (organizer, attendee count, keywords like "urgent" or "exec"). Low-priority conflicts are declined automatically with a courteous message; borderline or high-priority conflicts are surfaced to you in Slack so you decide.

When to use it

Use it if your calendar fills with optional syncs and standups that quietly eat the time you blocked for real work. It's for individual contributors and managers who set recurring focus blocks but get overridden by last-minute invites.

How it works

  1. 1A new or updated event on your Google Calendar triggers the run.
  2. 2The flow checks whether the event overlaps any event titled as a focus block.
  3. 3If it overlaps, a scoring step weighs organizer seniority, attendee count, and subject keywords to classify the invite as low or high priority.
  4. 4Low-priority invites are declined through Google Calendar with a templated decline note.
  5. 5High-priority or ambiguous conflicts are posted to your Slack DM with Accept/Decline context so you can act manually.

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.