IT OPS

Outlook Room Nightly Double-Booking Audit

Runs every night across all managed room mailboxes, finds every overlapping reservation for the next 14 days, writes them to a Postgres conflicts table.

CategoryIT Ops
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNightly schedule fires
  • ActionPull 14-day bookings for all room mailboxesOutlook
  • LogicCompute pairwise overlaps per room
  • ActionUpsert conflicts into Postgres tablePostgreSQLPostgres
  • OutputEmail prioritized morning digest to facilitiesOutlook

What it does

This is the scheduled safety net that catches conflicts real-time triggers miss — bookings made offline, imported from migrations, or created before monitoring was enabled. Each night it sweeps every room mailbox for the next two weeks, identifies all overlapping reservations, persists them to a Postgres table for tracking and trend reporting, and sends facilities a ranked digest of what needs fixing before the day starts.

When to use it

Use it as a daily reconciliation pass alongside or instead of real-time detection, especially when you need an auditable record of conflicts over time. Ideal for IT-Ops teams reporting on room-utilization health.

How it works

  1. 1A nightly schedule kicks off the audit.
  2. 2The flow pulls upcoming bookings for every managed room mailbox across the next 14 days.
  3. 3It computes all pairwise time overlaps per room.
  4. 4Each conflict is upserted into a Postgres `room_conflicts` table with a stable key so repeats aren't duplicated.
  5. 5A digest, sorted by soonest collision and number of attendees affected, is emailed to the facilities distribution list.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect OutlookMail, calendar, contacts.
  2. 2
    Connect PostgresAny Postgres URL — query, write, migrate.
  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.