TICKET MANAGEMENT
Roll up duplicate Front bug reports into one Linear issue
When a Front conversation is tagged as a bug, it finds other recent bug tickets describing the same defect and links them all to a single Linear issue.
How it runs
The automated pipeline, trigger to output.
- TriggerFront conversation tagged 'bug'Front
- ActionEmbed and find matching bug reportsPostgres
- LogicCluster already mapped to a Linear issue?
- ActionCreate or reuse Linear issueLinear
- ActionLink Front conversation + update countFront
- OutputPersist conversation-to-issue mappingPostgres
What it does
This workflow consolidates duplicate bug reports. When an agent tags a Front conversation as a bug, it searches for other recent conversations describing the same defect and ties them all to one Linear issue, so engineering sees impact in one place instead of five separate tickets.
When to use it
Use it when support fields the same bug from many customers and engineering needs a single deduplicated issue with an accurate affected-user count rather than scattered duplicate reports.
How it works
- 1A Front rule fires the webhook when a conversation gets the "bug" tag.
- 2OpenAI embeds the report and a Postgres vector query finds other bug-tagged conversations describing the same defect.
- 3A logic step checks whether the matched cluster already maps to a Linear issue in Postgres.
- 4If no issue exists, the workflow creates a Linear issue summarizing the defect; otherwise it reuses the existing one.
- 5Each matched Front conversation gets a private comment linking it to the Linear issue, and the issue's affected-customer count is updated.
- 6The conversation-to-issue mapping is saved back to Postgres for future matches.
Set it up
What you configure once, before turning it on.
- 1Connect FrontShared inbox, conversations.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 4Connect LinearIssues, projects, cycles, triage.
- 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.