TICKET MANAGEMENT
Link Zendesk duplicate reports to one Linear bug
When a Zendesk ticket is tagged as a bug, finds the matching open Linear issue for the same defect, links the ticket to it, adds the requester as a Linear subscriber.
How it runs
The automated pipeline, trigger to output.
- TriggerZendesk ticket tagged as bugZendesk
- ActionSearch Linear for canonical bug issueLinear
- LogicExactly one match, else manual review
- ActionLink ticket and subscribe requesterLinear
- ActionPost Linear status as Zendesk noteZendesk
- OutputNotify support lead in SlackSlack
What it does
When support tags a Zendesk ticket as a known bug, this workflow finds the single open Linear issue tracking that defect, links the Zendesk ticket to it, and adds the affected customer's contact as a subscriber so they are notified when the fix ships. It then posts the current Linear status back into the Zendesk ticket as an internal note.
When to use it
Use it when many customers report the same bug through support. It collapses a pile of duplicate Zendesk tickets onto one engineering issue, gives support a live status line, and makes sure every affected requester is tracked against the canonical fix.
How it works
- 1A Zendesk ticket is tagged as a bug, triggering the flow.
- 2The flow searches Linear for the open issue matching the bug label or component.
- 3A branch confirms exactly one canonical issue exists; ambiguous matches route to manual review.
- 4It links the Zendesk ticket to the Linear issue and adds the requester as a subscriber.
- 5It writes the Linear status as an internal note on the Zendesk ticket.
- 6It notifies the support lead in Slack that another duplicate was consolidated.
Set it up
What you configure once, before turning it on.
- 1Connect ZendeskTickets, queues, knowledge base.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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.