SUMMARIZATION
Resolved Discord thread to Linear feature request
When a feedback thread is marked resolved in Discord, summarizes the whole conversation, classifies it as bug or feature.
How it runs
The automated pipeline, trigger to output.
- TriggerDiscord thread tagged resolvedDiscord
- ActionFetch full thread with repliesDiscord
- ActionSummarize and classify with OpenAIOpenAI
- LogicCheck Linear for duplicate issueLinear
- OutputCreate or comment on Linear issueLinear
What it does
It watches for feedback threads that get tagged as resolved or actionable in Discord, reads the entire thread, and produces a tight summary plus a classification (bug, feature request, or docs gap). That becomes a Linear issue with a clear title, the distilled context, and a link to the source thread — so nothing actionable evaporates after the conversation cools.
When to use it
Use this when your community discusses problems in long Discord threads but your engineering team works out of Linear. It closes the gap between "we talked about it" and "it's tracked."
How it works
- 1A Discord event fires when a thread receives the configured resolved tag.
- 2The workflow pulls the full thread, including replies and the original message.
- 3An OpenAI call summarizes the discussion, extracts the core request, and assigns a type and priority hint.
- 4A logic branch checks Linear for an existing open issue with a matching signature to avoid duplicates.
- 5If new, it creates a Linear issue with the summary, type label, and source link; if a match exists, it appends the new context as a comment.
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 Summarization workflows
On-submit Loom standup roll-up archived to Confluence
When a standup video is submitted via webhook, transcribes it, generates a per-person written summary, and appends it to a running team standup page in Confluence.
Front Escalation Handoff Doc in Notion
When a Front escalation closes, drafts a structured handoff document in Notion capturing the resolution, customer commitments, and open follow-ups, then alerts the AE in Slack.
Front Escalation War-Room Brief to Slack
On a Front escalation, posts a concise threat-assessment brief to a Slack channel only when the AI judges the situation high-severity.
VIP Front Escalation Instant Exec Page-Out
Detects escalations from VIP accounts in Front, generates a one-paragraph executive recap, and pages the named account exec via Slack and Salesforce task within minutes.
Release health note per Vercel deploy
When a Vercel deploy goes live, summarizes the Sentry errors observed in the release window into a plain-English health note that separates brand-new error classes…
Rollback recommendation when a deploy spikes errors
When a Sentry alert fires for an error spike, attributes it to the most recent deploy, summarizes whether the spike is dominated by new error classes introduced by that release.
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.