TICKET MANAGEMENT
Auto-Generated Vendor Work Orders from Photo Requests
Takes a photo-based maintenance request, classifies severity, generates a labeled annotated image of the issue.
How it runs
The automated pipeline, trigger to output.
- TriggerRequest received via webhookHTTP webhook
- ActionClassify trade and severity from photoOpenAI
- ActionGenerate annotated issue reference imageImage generation
- LogicAssemble work order fields
- OutputCreate vendor work order page in NotionNotion
What it does
Builds a complete, ready-to-send vendor work order from a single photo request. It classifies the problem, produces an annotated reference image highlighting the issue, and writes a structured work order page in Notion the vendor can open and act on.
When to use it
Use this when vendors need more than a one-line message, they need a documented work order with the issue called out visually, the trade, severity, location, and scope all in one place. Good for teams that hand work to external contractors.
How it works
- 1A webhook receives the request with the original photo and location.
- 2The photo is analyzed to classify the trade and severity.
- 3An annotated reference image is generated highlighting the damaged area for the vendor.
- 4A logic step assembles the work order fields: trade, severity, scope notes, and target completion.
- 5A structured work order page is created in Notion with the annotated image and dispatch details for the assigned vendor.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect Image generationManaged Nano Banana image renders, metered per image.
- 4Connect NotionPages, databases, comments.
- 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.
Software
AI Tools Startup
Ship an AI tool, distribute on every channel, watch the unit economics.
Creator
AI Image / Video Studio
Logos, marketing graphics, product shots, and video — generated, curated, and shipped on tap.
Creator
Social Manager
Draft, approve, schedule, and measure social posts across 8 channels.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.