TICKET MANAGEMENT
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.
How it runs
The automated pipeline, trigger to output.
- TriggerDesignated emoji reaction added in DiscordDiscord
- LogicVerify reactor is a moderator and emoji matches
- ActionFetch reacted message plus surrounding contextDiscord
- ActionDraft structured issue title, body, and checklist with LLMOpenAI
- ActionCreate Linear issue assigned to triageLinear
- OutputReply under the original Discord message with linkDiscord
What it does
Lets a trusted moderator turn any Discord message into a Linear issue simply by reacting with a chosen emoji (for example a ticket or bug emoji). The flow grabs the reacted message and recent context, has an LLM write a clean title, description, and acceptance checklist, then files it in Linear. The bot replies in-channel with the issue link.
When to use it
Use it when not every bug-channel message deserves a ticket and you want a human curation step. Instead of auto-filing everything, your team flags the real signal with a reaction, keeping Linear clean while staying one click away from formal tracking.
How it works
- 1A reaction-added event with the designated emoji triggers the flow.
- 2A logic step verifies the reactor is an allowed moderator and the emoji matches.
- 3The flow fetches the reacted message plus a few surrounding messages for context.
- 4An OpenAI call drafts a structured title, description, and checklist.
- 5A Linear issue is created and assigned to the triage workflow.
- 6The bot replies under the original message with the issue link.
Set it up
What you configure once, before turning it on.
- 1Connect DiscordCommunity channels + voice + bots.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect LinearIssues, projects, cycles, triage.
- 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
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.
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.
Front Duplicate Conversation Clusterer
When a new Front conversation arrives, it semantically compares the report against open conversations.
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.