PERSONAL PRODUCTIVITY

Auto-decline invites that overlap a protected deep-work hold

When a new meeting invite lands on your calendar, this checks whether it overlaps an active deep-work hold and automatically declines it with a polite note pointing to your next…

CategoryPersonal Productivity
Enginesim
Difficultybeginner
Triggerevent
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew calendar invite receivedGoogle CalendarGoogle Calendar
  • ActionFetch today's deep-work holdsGoogle CalendarGoogle Calendar
  • LogicDoes the invite overlap a protected hold?
  • ActionFind next open slot after the blockGoogle CalendarGoogle Calendar
  • OutputDecline invite with suggested alternative timeGoogle CalendarGoogle Calendar

What it does

Watches your primary calendar for incoming invites and protects any event tagged as a deep-work focus block. If a new invite overlaps a protected hold, it declines on your behalf and sends the organizer a short, friendly note proposing your next free window instead of leaving them guessing.

When to use it

For makers and individual contributors who reserve recurring focus blocks but keep getting double-booked. Run it when you want your calendar to defend itself without you triaging every ping.

How it works

  1. 1A new event is created on your Google Calendar, firing the trigger.
  2. 2The flow loads your focus-block holds for that day and checks the new invite's start and end times against them.
  3. 3A branch decides: if there's no overlap, it exits quietly and leaves the invite untouched.
  4. 4If it overlaps a protected hold, the flow finds your next open slot after the block ends.
  5. 5It declines the invite through Google Calendar and writes a reply with the suggested alternative time.
  6. 6The organizer receives the decline plus your proposed slot in one motion.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect Google CalendarEvents, attendees, availability.
  2. 2
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  3. 3
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  4. 4
    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.