TICKET MANAGEMENT
Triage photo maintenance requests into routed work orders
An agent monitors a facilities inbox for emailed photos of broken assets, uses vision to identify the problem and trade.
How it runs
The automated pipeline, trigger to output.
- TriggerPhoto email arrives in inboxGmail
- ActionIdentify asset + problem via visionOpenAI
- LogicSelect vendor list by trade
- ActionCreate Trello work order with photoTrello
- ActionLink issue to asset in AirtableAirtable
- OutputReply to sender confirming receiptGmail
What it does
Handles the common case where a tenant just snaps a photo and emails it with little text. The agent inspects the image, identifies the affected asset and likely trade, drafts a clear problem description, opens a Trello work order on the right vendor list, and links the issue back to the asset's row in Airtable.
When to use it
Use it when maintenance reports arrive mostly as photos rather than detailed descriptions, and you want the system to do the interpretation work that staff would otherwise do by eye. Good for property managers tracking physical assets in Airtable.
How it works
- 1An email with one or more photo attachments arrives in the facilities inbox.
- 2The agent runs vision analysis to identify the asset, the visible problem, and the responsible trade.
- 3It writes a structured work-order description and chooses the matching Trello vendor list.
- 4A Trello card is created with the photo and description attached.
- 5The agent finds or creates the asset in Airtable and appends the open issue, then replies to the sender confirming receipt.
Set it up
What you configure once, before turning it on.
- 1Connect GmailRead, draft, send, label.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect TrelloKanban boards for everything.
- 4Connect AirtableBases, tables, views, automations.
- 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.
