OTHER

Flag Recurring Room Holds That Are Chronically Empty

Weekly, scans recurring room reservations against check-in history and flags series with persistently low attendance so owners can shrink or cancel standing holds.

CategoryOther
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly audit schedule
  • ActionList recurring events over review windowGoogle CalendarGoogle Calendar
  • ActionJoin with check-in history in AirtableAirtableAirtable
  • LogicKeep series below utilization threshold
  • ActionLog flagged series to audit tableAirtableAirtable
  • OutputPrompt owners in Teams to actMicrosoft Teams

What it does

Hunts down zombie recurring bookings. It looks back over several weeks of check-in data for each standing room series, calculates the real attendance rate, and surfaces the recurring holds that almost never get used so their owners can release the room permanently.

When to use it

Use this when standing weekly meetings quietly lock up your best rooms whether or not anyone shows. It targets the structural waste that one-off no-show releases miss, prompting owners to cancel or downsize dead series.

How it works

  1. 1A weekly schedule fires (e.g. Friday afternoon).
  2. 2The workflow lists recurring room events from Google Calendar over the trailing review window.
  3. 3It joins each series against check-in history stored in Airtable to compute an attendance rate.
  4. 4A filter keeps only series below the utilization threshold (e.g. under 30 percent attended).
  5. 5It logs each flagged series with its stats to an Airtable audit table.
  6. 6It messages each series owner in Microsoft Teams with the numbers and a prompt to keep, shrink, or cancel the recurring hold.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect Google CalendarEvents, attendees, availability.
  2. 2
    Connect AirtableBases, tables, views, automations.
  3. 3
    Connect Microsoft TeamsChannels, chats, files.
  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.