SOCIAL MEDIA
Discord Reaction-Spike to Auto-Filed Linear Issue
When a Discord message crosses a negative-reaction threshold, classifies whether it describes a real product problem and, if so, opens a deduplicated Linear issue tagged…
How it runs
The automated pipeline, trigger to output.
- TriggerDiscord message crosses negative-reaction thresholdDiscord
- ActionClassify complaint type and infer owning teamOpenAI
- LogicDrop non-complaints; dedupe against existing Linear issuesLinear
- ActionCreate labeled Linear issue with source linkLinear
- OutputReturn new issue linkLinear
What it does
This workflow turns a sudden pile-up of negative reactions on a Discord message into a tracked product issue. The moment a message accumulates enough thumbs-down, angry, or downvote reactions to clear your threshold, the workflow asks an LLM whether it actually describes a bug or product complaint (versus a joke or off-topic gripe). If it does, it files a Linear issue with the message text, link, and an inferred team label — skipping creation if a similar issue already exists.
When to use it
Use it when your community signals problems through reactions faster than they file tickets, and you want those signals to land in your engineering tracker automatically without spamming it with noise or duplicates.
How it works
- 1A Discord reaction event triggers when a message's negative-reaction count crosses the configured threshold.
- 2OpenAI classifies whether the message is a genuine product complaint and infers the responsible team.
- 3A logic step drops non-complaints and checks Linear for an existing similar issue.
- 4If it is a new, real complaint, a Linear issue is created with the source text, message link, and team label.
- 5The created issue link is delivered as the final output.
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 Social Media workflows
Discord event capacity gate with automatic waitlist promotion
Enforces a seat cap on RSVPs: once an event is full, new sign-ups join a waitlist, and when someone drops out the next person is promoted, notified in Discord.
Tiered Discord event reminder fan-out (24h / 1h / live)
On a schedule, scans upcoming Discord-tracked events and DMs each confirmed attendee staged reminders at 24 hours, 1 hour, and event start.
A/B carousel cover variants from one brief
Takes a single approved brief and uses an LLM to write three distinct cover-slide headlines, renders a carousel cover for each, and logs the variants to Airtable for an A/B test.
Localized carousel variants per target market
From one approved master brief, translates the copy into each target locale, renders a localized carousel per market, and publishes each to its region's platform account.
Carousel render and auto-publish on Slack approval
Renders carousel variants from a brief, posts a preview to Slack for a one-click approve, and on approval publishes the chosen variant to the connected social platforms.
Discord /rsvp slash command with Outlook calendar invite
Lets members RSVP to an event via a /rsvp slash command, captures their status (yes/maybe/no), and sends a matching Outlook calendar invitation or cancellation to their email.
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.