IT OPS
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.
How it runs
The automated pipeline, trigger to output.
- TriggerOutlook conflicting room booking detectedOutlook
- LogicSelect meeting to move and find best free room
- ActionSend approval card to organizer in TeamsMicrosoft Teams
- LogicBranch on approve, decline, or timeout
- ActionRebook in Outlook on approvalOutlook
- OutputConfirm in Teams or escalate to facilitiesMicrosoft Teams
What it does
Adds a consent step to conflict resolution. On a room clash it computes the best alternative room but does not move anything yet — it sends the affected organizer an approval prompt in Microsoft Teams. If they accept, the meeting is rebooked; if they decline or time out, facilities is alerted to mediate manually.
When to use it
Use this for VIP or sensitive meetings where silently moving someone's room would be unacceptable, but you still want the system to do the legwork of finding the alternative and executing the change once a human says yes.
How it works
- 1Outlook fires on a conflicting room booking.
- 2A logic step picks the meeting to move and finds the best comparable free room.
- 3The flow sends the organizer an approval card in Microsoft Teams with the proposed new room.
- 4A logic branch waits for the response: approve, decline, or timeout.
- 5On approve, it rebooks the meeting in Outlook and confirms in Teams; on decline or timeout, it escalates to the facilities channel for manual handling.
Set it up
What you configure once, before turning it on.
- 1Connect OutlookMail, calendar, contacts.
- 2Connect Microsoft TeamsChannels, chats, files.
- 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
Recurring Sensor Fault Root-Cause Investigator
On a schedule, an agent reviews recent Monday work orders and BigQuery telemetry to identify equipment with repeating faults, drafts a root-cause hypothesis with a recommended fix.
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.
Agentic Inactive-Seat Reclamation Review
An agent investigates each idle SaaS seat by correlating SSO login gaps with HR status and ticket history, classifies it as reclaim, hold, or escalate, and drafts a reasoned…
Reconcile SSO logins against expense spend to find unmanaged tools
Joins SSO usage data with expense/payment records in Snowflake to surface tools that are being used but not paid for, or paid for but never logged.
Approved-Seat Deprovision Execution
Fires when an IT approver confirms a seat for removal, then executes deprovisioning via the IdP API and logs the action to an audit table and a Linear cleanup ticket.
HVAC Anomaly Detection to Severity-Routed Work Orders
Ingests building HVAC telemetry via webhook, flags out-of-band temperature, pressure, or runtime readings.
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.