IT OPS
Teams Room Conflict Triage Bot
Lets coordinators report a room clash from a Teams message; the agent looks up both meetings in Outlook, proposes the best fix.
How it runs
The automated pipeline, trigger to output.
- TriggerConflict reported in Teams triage channelMicrosoft Teams
- ActionLook up competing meetings in OutlookOutlook
- OutputPost recommended fix and request approval reactionMicrosoft Teams
- LogicGate on approval; stop on rejection
- ActionReschedule chosen meeting and notify both organizersOutlook
What it does
This turns Microsoft Teams into the front door for room-conflict triage. A coordinator flags a clash (or forwards a complaint) in a designated Teams channel; the agent identifies the two meetings in Outlook, recommends which to move and where, and waits for an approval reaction. On approval it actually moves the meeting and messages both organizers with the new details — closing the loop without anyone touching Outlook directly.
When to use it
Use it when conflicts are reported by people, not just detected by systems, and you want a conversational, approve-then-act workflow inside the tool your team already lives in. Best for IT-Ops or workplace teams that prefer human-in-the-loop control.
How it works
- 1A message in the Teams triage channel triggers the flow.
- 2The agent parses the room and time, then looks up the competing meetings in Outlook.
- 3It posts a recommended resolution and asks for an approval reaction.
- 4A logic gate waits for approval; on rejection it stops and asks for guidance.
- 5On approval it reschedules the chosen meeting in Outlook and notifies both organizers in the thread.
Set it up
What you configure once, before turning it on.
- 1Connect Microsoft TeamsChannels, chats, files.
- 2Connect OutlookMail, calendar, contacts.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.