TICKET MANAGEMENT
Notify Front customers when their promoted Linear bug is marked Done
When a Linear bug that was promoted from Front moves to Done, it drafts a personalized resolution reply and queues it as a draft on each linked Front conversation for an agent…
How it runs
The automated pipeline, trigger to output.
- TriggerLinear issue moved to DoneLinear
- LogicFilter: only Front-promoted issues
- ActionResolve linked Front conversation IDsFront
- ActionDraft personalized resolution replyOpenAI
- OutputStage reply as Front draftFront
What it does
Closes the loop back to the customer. When a Linear issue that originated from Front transitions to Done, the workflow finds every Front conversation linked to that issue, has an LLM draft a warm, specific resolution message for each, and stages it as a Front draft so an agent can review and send.
When to use it
Use it when bugs get fixed but customers never hear back, hurting trust and reopening tickets. This makes the resolution reply automatic to draft while keeping a human in the loop on the actual send.
How it works
- 1A Linear webhook fires when an issue moves to the Done state.
- 2A filter checks the issue carries the Front-origin metadata; non-promoted issues are skipped.
- 3The workflow reads the issue's linked Front conversation IDs from its description.
- 4For each conversation, an OpenAI call drafts a resolution reply referencing the original report and the fix.
- 5Each reply is created as a draft on its Front conversation for agent review and send.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect FrontShared inbox, conversations.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Ticket Management workflows
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.
Front-to-Linear Recurring Bug Linker
When a Front ticket is tagged as a bug, it searches Linear for an existing matching issue and either links the ticket to that parent issue or opens a new tracked one.
Front Duplicate Conversation Clusterer
When a new Front conversation arrives, it semantically compares the report against open conversations.
Intercom Known-Issue Auto-Responder
When a new Intercom conversation matches a known active incident, it attaches the conversation to that incident's parent ticket and sends the customer the current status reply.
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.
Escalate repeat reopens to a Linear bug
Detects when the same underlying issue reopens across multiple tickets, uses an AI agent to cluster them by root cause.
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.