TICKET MANAGEMENT
Turn maintenance request emails into triaged work orders
Reads inbound facilities request emails, uses AI to extract the asset, location, and severity, logs a structured work order in Airtable.
How it runs
The automated pipeline, trigger to output.
- TriggerNew request email receivedGmail
- ActionExtract asset, location, severity with AIOpenAI
- LogicMatch location to building, crew, and SLA tier
- ActionWrite structured work order to AirtableAirtable
- OutputCreate Trello card on building boardTrello
What it does
Converts free-text maintenance emails into clean, structured work orders. An AI step parses the unstructured message into asset, building, fault, and severity fields, removing manual re-keying from the intake desk.
When to use it
Use it when tenants and staff still email repair requests in plain language and someone has to read each one and open a ticket. This automates that triage while preserving the original email for reference.
How it works
- 1A new email arriving in the facilities inbox triggers the flow.
- 2An AI step extracts asset name, location, fault description, and inferred severity from the email body.
- 3The extracted location is matched to a building and crew, and an SLA tier is assigned.
- 4A structured work-order row is written to Airtable with the parsed fields and source email.
- 5A Trello card is created on the building's board, tagged with severity and crew, ready to dispatch.
Set it up
What you configure once, before turning it on.
- 1Connect GmailRead, draft, send, label.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect AirtableBases, tables, views, automations.
- 4Connect TrelloKanban boards for everything.
- 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 Ticket Management workflows
Deduplicate Discord bug reports against existing Linear issues
Before creating anything, searches Linear for issues matching a new Discord bug report; if a duplicate exists it comments and links the report there, otherwise it opens a fresh…
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.
Promote a Discord message to a Linear issue via an emoji reaction
When a moderator adds a designated emoji reaction to any Discord message, an LLM converts that message into a structured Linear issue and threads the link back.
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.
Route Discord bug reports by severity to Linear or PagerDuty
Classifies each Discord bug report by severity using an LLM, then files normal bugs as Linear issues while escalating critical outages to a PagerDuty incident so on-call gets…
Triage Discord bug threads into structured Linear issues with repro checklists
Watches a Discord bug-report channel, uses an LLM to extract a clean title, severity, and step-by-step reproduction checklist from the messy thread.
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.