TICKET MANAGEMENT
Route facility work orders by location and severity SLA
Catches inbound maintenance requests via webhook, looks up the asset's building and zone.
How it runs
The automated pipeline, trigger to output.
- TriggerWork-order request receivedHTTP webhook
- ActionResolve asset to building, zone, and crewAirtable
- LogicCompute SLA tier and due-by from severity
- ActionCreate Trello card on building's boardTrello
- OutputReturn work-order ID and SLA deadlineHTTP webhook
What it does
Turns raw maintenance requests into triaged, SLA-stamped work orders. Each request is matched to its physical asset and severity, given a deadline, and dropped onto the correct facilities Trello board so the right crew picks it up immediately.
When to use it
Use it when tenants, staff, or building sensors submit repair requests through a form or portal and you need consistent triage instead of an overflowing shared inbox. Ideal for property managers and facilities teams juggling multiple buildings with different response commitments.
How it works
- 1A webhook receives the request payload (asset ID, description, reported severity).
- 2The asset ID is looked up in Airtable to resolve building, zone, and assigned crew.
- 3A branch evaluates severity against the SLA matrix to compute a due-by timestamp (e.g. 4h critical, 24h high, 72h standard).
- 4A Trello card is created on the building's board with the due date, crew, and zone labels.
- 5A confirmation with the work-order ID and SLA deadline is posted back to the requester.
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 TrelloKanban boards for everything.
- 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 Ticket Management workflows
Enrich Discord bug reports with Sentry errors before filing in Linear
Takes a Discord bug report, has an LLM pull out likely error signatures, searches Sentry for matching events.
Front-to-Linear Recurring Bug Linker
When a Front ticket is tagged as a bug, it searches Linear for an existing matching issue and either links the ticket to that parent issue or opens a new tracked one.
Front Duplicate Conversation Clusterer
When a new Front conversation arrives, it semantically compares the report against open conversations.
Intercom Known-Issue Auto-Responder
When a new Intercom conversation matches a known active incident, it attaches the conversation to that incident's parent ticket and sends the customer the current status reply.
Weekly reopen-by-agent coaching digest
Aggregates each agent's solved-then-reopened tickets for the week, identifies the most common reopen reason per agent, and emails a private coaching digest to the support manager.
Escalate repeat reopens to a Linear bug
Detects when the same underlying issue reopens across multiple tickets, uses an AI agent to cluster them by root cause.
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.
