PERSONAL PRODUCTIVITY

Focus-Block Invite Defender

Watches your calendar for new meeting invites that overlap your protected focus blocks and auto-declines the low-priority ones with a polite note.

CategoryPersonal Productivity
Enginesim
Difficultyintermediate
Triggerevent
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew or updated calendar invite receivedGoogle CalendarGoogle Calendar
  • LogicDoes it overlap a protected focus block?
  • ActionScore priority against weekly intentOpenAI
  • LogicBranch: auto-decline vs. escalate
  • ActionDecline low-priority invite with noteGoogle CalendarGoogle Calendar
  • OutputPost borderline cases to Slack for a decisionSlack

What it does

Protects the deep-work blocks you put on your calendar. Whenever a new invite lands on top of one, it scores the meeting against your stated weekly intent and either declines it automatically with a courteous message, or pings you to make the call yourself.

When to use it

Use it when your focus time keeps getting eaten by reflexive meeting invites and you want a consistent gatekeeper instead of manually triaging every overlap. Best for individual contributors and managers who block recurring maker-time.

How it works

  1. 1A new or updated event on your Google Calendar fires the trigger.
  2. 2A logic step checks whether the invite overlaps an event titled with your focus-block marker (e.g. "[Focus]").
  3. 3If it overlaps, an OpenAI step reads the invite title, organizer, attendee count, and your weekly intent note, then returns a priority score and a draft decline reason.
  4. 4A logic branch splits on the score: clearly low priority goes straight to decline.
  5. 5The action declines the event in Google Calendar with the generated note.
  6. 6Borderline invites are posted to Slack with Accept/Decline buttons so you decide in one click.

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.