IT OPS
Triage field voice reports: urgent ones page on-call, rest go to Trello
Transcribes an inbound field voice report, classifies its urgency with OpenAI, and either pages the on-call responder via PagerDuty for emergencies or files a standard Trello…
How it runs
The automated pipeline, trigger to output.
- TriggerInbound voice report (webhook)HTTP webhook
- ActionTranscribe with ElevenLabsElevenLabs
- ActionClassify urgency with OpenAIOpenAI
- LogicBranch on critical vs. routine
- ActionPage on-call via PagerDuty (critical)PagerDuty
- OutputFile routine Trello cardTrello
What it does
Listens for field voice reports, decides whether each one is an emergency or routine, and routes accordingly. Critical reports (safety hazards, outages, blockers) page the on-call person immediately; everything else becomes a normal Trello task so the queue stays clean.
When to use it
Use it when field staff report a mix of routine updates and genuine emergencies through the same channel, and you cannot afford to bury an urgent hazard inside a backlog of ordinary notes.
How it works
- 1An inbound voice report arrives via webhook.
- 2ElevenLabs transcribes the recording.
- 3OpenAI classifies urgency (critical vs. routine) and drafts a one-line summary.
- 4A logic branch checks the urgency label.
- 5If critical, PagerDuty raises an incident assigned to the on-call rotation.
- 6If routine, Trello creates a card on the team's intake board with the transcript attached.
Set it up
What you configure once, before turning it on.
- 1Connect ElevenLabsText-to-speech, voice cloning.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect TrelloKanban boards for everything.
- 4Connect PagerDutyIncidents, on-call, escalations.
- 5Connect HTTP webhookTrigger any URL on agent actions.
- 6Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 7Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 8Test, 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.