IT OPS
Vercel Domain Verification Failure Auto-Pager
Listens for Vercel deployment and domain webhooks and immediately pages on-call when a domain reports a verification or misconfiguration error.
How it runs
The automated pipeline, trigger to output.
- TriggerVercel webhook received (HTTP)HTTP webhook
- LogicFilter to verification/misconfiguration events
- ActionEnrich with required records from VercelVercel
- ActionTrigger high-urgency PagerDuty incidentPagerDuty
- OutputMirror alert to Microsoft TeamsMicrosoft Teams
What it does
This is an event-driven responder rather than a scheduled scan. It receives Vercel webhook events for domain and deployment changes, isolates the ones that signal a domain is unverified or misconfigured, and pages on-call in real time so a broken domain is caught within seconds of going bad rather than at the next daily sweep.
When to use it
Use it for high-traffic or revenue-critical domains where the delay of a scheduled check is unacceptable. It complements the daily watchdog: the schedule catches slow drift, this catches sudden breakage the moment Vercel observes it.
How it works
The webhook trigger receives Vercel events at an HTTP endpoint with signature verification. A logic step filters to `domain.created`, `domain.verification.failed`, and deployment events carrying a misconfigured-domain flag, dropping everything else. For a qualifying event, an action enriches it by fetching the domain's current required records from Vercel. An action then triggers a high-urgency PagerDuty incident including the offending domain and the records that must be set. A final output mirrors the alert to a Microsoft Teams channel for broad team visibility.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect VercelDeploys, runtime logs, analytics.
- 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.