IT OPS
Look up the on-call vendor for a zone and dispatch the alert
Takes a facilities alert, looks up which vendor owns the affected zone and system from an Airtable vendor directory.
How it runs
The automated pipeline, trigger to output.
- TriggerFacilities alert hits webhookHTTP webhook
- ActionLook up vendor and service for zoneAirtable
- LogicConfirm match or use fallback owner
- ActionDispatch page to vendor PagerDuty servicePagerDuty
- OutputWrite work-order back to directoryAirtable
What it does
Closes the gap between a generic alert and knowing who to call. When an alert names a building, zone, and system type, this workflow queries an Airtable vendor directory to find the contracted vendor and their on-call service for that exact scope, then dispatches the page to the correct PagerDuty service and opens a work-order record so the dispatch is tracked end to end.
When to use it
Use this when different vendors cover different systems or buildings (one firm for chillers, another for elevators, a third for electrical) and the right routing depends on a lookup rather than a fixed rule. It removes the manual "who covers this?" step.
How it works
- 1A facilities alert arrives at the webhook with building, zone, and system type.
- 2An Airtable lookup matches the zone and system to the responsible vendor and their PagerDuty service key.
- 3A logic step confirms a vendor was found, branching to a fallback owner if not.
- 4The alert is dispatched to the matched vendor's PagerDuty service.
- 5A work-order row is written back to Airtable linking the alert, vendor, and dispatch time.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect AirtableBases, tables, views, automations.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 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
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.
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.
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.
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.
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.
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.