PERSONAL PRODUCTIVITY

Auto-decline focus-block invites unless the organizer is a VIP

Declines meetings that overlap your focus blocks by default, but routes invites from people on your VIP allowlist to a Slack approval prompt so important asks never get…

CategoryPersonal Productivity
Enginesim
Difficultybeginner
Triggerevent
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew calendar invite receivedGoogle CalendarGoogle Calendar
  • LogicOverlaps a focus block?
  • LogicOrganizer on VIP allowlist?
  • ActionDecline non-VIP inviteGoogle CalendarGoogle Calendar
  • OutputEscalate VIP invite to SlackSlack

What it does

Applies a defend-by-default rule with a trusted-people exception. Any invite landing on a focus block is declined automatically, except when the organizer is on a VIP allowlist (your manager, key clients, direct reports). Those get held and surfaced to you for a quick accept-or-decline decision, so the system protects your time aggressively without burning your most important relationships.

When to use it

You're comfortable auto-declining most meeting creep but a blanket rule is too blunt — there are a handful of people whose invites should always reach a human. Use this when relationship nuance matters more than pure calendar hygiene.

How it works

  1. 1A new Google Calendar invite triggers the workflow.
  2. 2The flow checks whether it overlaps a focus block; non-overlapping invites are ignored.
  3. 3It compares the organizer's email against a VIP allowlist.
  4. 4Branch A (non-VIP): the invite is declined immediately with a polite auto-note.
  5. 5Branch B (VIP): the workflow posts the invite details to Slack with accept/decline actions for your manual call.

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.