SOCIAL MEDIA
Hourly Discord Sentiment-Shift Cluster Digest to Slack
Every hour, pulls recent Discord messages and reactions, clusters them into emerging complaint themes.
How it runs
The automated pipeline, trigger to output.
- TriggerHourly schedule fires
- ActionFetch recent Discord messages + reactionsDiscord
- ActionCluster messages into complaint themes and score sentimentOpenAI
- LogicKeep only clusters trending more negative than prior hour
- OutputPost ranked sentiment-shift digest to SlackSlack
What it does
This workflow gives your team an hourly early-warning read on community mood. It collects the last hour of messages and reaction counts from your Discord channels, uses an LLM to group them into distinct complaint clusters (e.g. "billing confusion", "login errors"), and scores each cluster's sentiment trend against the prior hour. If negative sentiment is climbing, it posts a tight, ranked digest to a Slack channel so the team sees the shift before it becomes a fire.
When to use it
Use it when your community lives in Discord and you want a low-noise heads-up the moment frustration starts clustering — without a human reading every channel. Best for community, support, and product teams who only want to be pinged when something is actually trending worse.
How it works
- 1A schedule fires every hour.
- 2Discord messages and reaction tallies from the watched channels are fetched for the window.
- 3OpenAI clusters the messages into named complaint themes and rates each cluster's sentiment.
- 4A logic step compares each cluster's negative volume to the prior hour and keeps only those trending upward.
- 5If any rising clusters remain, a ranked digest is posted to Slack; otherwise the run ends silently.
Set it up
What you configure once, before turning it on.
- 1Connect DiscordCommunity channels + voice + bots.
- 2Connect OpenAIModels, embeddings, files.
- 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 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.
