IT OPS
Outlook-to-Google Cross-Calendar Room Conflict Rebooker
In hybrid offices running both Outlook and Google room calendars, detects a clash on a shared Outlook room and rebooks the bumped meeting into an available Google Workspace room.
How it runs
The automated pipeline, trigger to output.
- TriggerOutlook room booking overlaps existing eventOutlook
- LogicConfirm overlap and choose meeting to relocate
- ActionFind free comparable Google Workspace roomGoogle Calendar
- ActionCreate meeting on Google room calendarGoogle Calendar
- ActionUpdate Outlook invite location and release old slotOutlook
- OutputNotify organizer in Slack with both linksSlack
What it does
Bridges two calendar systems. When an Outlook room booking collides with another, the flow searches Google Workspace room calendars for an equivalent open space and moves the bumped meeting there — then writes the new location back onto the Outlook invite so attendees see one source of truth.
When to use it
Use this after a merger or in offices that never fully consolidated calendars, where some rooms live in Outlook and some in Google Calendar, and conflicts can only be resolved by spilling across systems.
How it works
- 1Outlook fires on a room booking that overlaps an existing event.
- 2A logic step confirms the overlap and selects the meeting to relocate.
- 3The flow queries Google Calendar room resources for a free comparable room in the same window.
- 4It creates the meeting on the Google room calendar with the original attendees.
- 5It updates the Outlook invite's location to the new Google room and releases the old slot.
- 6The organizer is notified in Slack with both calendar links.
Set it up
What you configure once, before turning it on.
- 1Connect OutlookMail, calendar, contacts.
- 2Connect Google CalendarEvents, attendees, availability.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More IT Ops workflows
Daily Building Anomaly Digest to MS Teams
Each morning queries BigQuery for the prior day's flagged sensor anomalies, summarizes them by site and system into a ranked briefing.
Indoor Air Quality Breach to Tenant Notice and Work Order
Listens for CO2, VOC, or humidity sensor alerts via webhook, and when a zone exceeds occupant-safety limits it emails affected tenants, opens a Monday remediation task.
Self-Service Reclaim Email for Idle Users
Detects users idle in a SaaS app past the threshold and emails each one a keep-or-release link; unanswered seats after the deadline are auto-flagged for removal.
Outlook Room Conflict Resolver with Approval Gate in Teams
When an Outlook room clashes, proposes a rebooking and asks the bumped meeting's organizer to approve the move in Microsoft Teams before any change is made.
Outlook Room Double-Booking Resolver with Auto-Rebook
Detects when two meetings claim the same Outlook room resource and automatically relocates the lower-priority meeting to a comparable free room.
Monthly Wasted-License Cost Report
Aggregates inactive-seat data across all tracked SaaS apps each month, computes total reclaimable spend, and delivers a ranked cost report to leadership in Notion and Slack.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.