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.

CategoryTicket Management
Enginesim
Difficultyintermediate
Triggerwebhook
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWork-order request receivedHTTP webhook
  • ActionResolve asset to building, zone, and crewAirtableAirtable
  • LogicCompute SLA tier and due-by from severity
  • ActionCreate Trello card on building's boardTrelloTrello
  • 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

  1. 1A webhook receives the request payload (asset ID, description, reported severity).
  2. 2The asset ID is looked up in Airtable to resolve building, zone, and assigned crew.
  3. 3A branch evaluates severity against the SLA matrix to compute a due-by timestamp (e.g. 4h critical, 24h high, 72h standard).
  4. 4A Trello card is created on the building's board with the due date, crew, and zone labels.
  5. 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.

  1. 1
    Connect HTTP webhookTrigger any URL on agent actions.
  2. 2
    Connect AirtableBases, tables, views, automations.
  3. 3
    Connect TrelloKanban boards for everything.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.