IT OPS
Escalate failed shared-mailbox provisioning to PagerDuty with diagnostics
Triggered when a provisioning run reports failure, it captures the Exchange error, posts diagnostics to Teams.
How it runs
The automated pipeline, trigger to output.
- TriggerProvisioning failure event received via webhookHTTP webhook
- ActionRe-query Exchange Online for mailbox state and error detailShell
- LogicClassify failure as benign duplicate or real incident
- ActionOpen PagerDuty incident with diagnosticsPagerDuty
- OutputLink incident in Teams IT Operations channelMicrosoft Teams
What it does
Catches shared-mailbox provisioning failures and routes them intelligently: benign cases like an already-existing alias are logged quietly, while real failures page the on-call IT engineer with full diagnostics.
When to use it
Use this alongside any automated provisioning flow so silent failures never leave a department waiting on a mailbox that was never created. It separates noise from genuine incidents that need a human.
How it works
- 1A provisioning job emits a failure event to the workflow webhook with the alias and raw Exchange error.
- 2A shell step re-queries Exchange Online to capture mailbox state and the full error detail.
- 3A logic step classifies the failure: duplicate/already-exists is treated as benign, everything else as an incident.
- 4Benign cases post a short note to Teams and stop.
- 5For real failures, a PagerDuty action opens an incident with the alias, error, and diagnostics attached.
- 6A final Teams message links the PagerDuty incident in the IT Operations channel so the team has context.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect ShellRun sandboxed commands inside the workspace.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 4Connect Microsoft TeamsChannels, chats, files.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.