SOCIAL MEDIA
Cross-channel pile-on correlator
Pulls both Discord chatter and scraped social mentions, detects when the same complaint is flaring on multiple channels at once.
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule fires correlation pass
- ActionPull recent Discord messagesDiscord
- ActionPull social mentionsApify
- ActionCluster into shared topics and score heatOpenAI
- LogicTopic hot on both channels? Pick owning lead
- OutputRoute correlated pack to matched owner in SlackSlack
What it does
Most detectors watch one surface. This one fuses Discord and public social mentions, then looks for the dangerous signal: the same grievance spiking on both at the same time. A complaint trending in two places is a real pile-on, not noise — and it routes that correlated event to whichever comms owner covers the affected topic.
When to use it
Use this when your community spans Discord and public social, and you want to cut false alarms by only paging when a complaint corroborates across channels.
How it works
- 1A schedule fires to begin a correlation pass.
- 2Discord recent messages and Apify social mentions are pulled in parallel.
- 3OpenAI clusters both streams into shared complaint topics and scores each topic's heat.
- 4A logic step flags any topic that is hot on both channels at once and picks the owning comms lead.
- 5OpenAI builds a correlated context pack showing the topic across both surfaces.
- 6The pack is routed to the matched owner's Slack DM or channel.
Set it up
What you configure once, before turning it on.
- 1Connect DiscordCommunity channels + voice + bots.
- 2Connect ApifyActors, scrapers, datasets.
- 3Connect OpenAIModels, embeddings, files.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Social Media workflows
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.
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.
Agent-Driven Comment Policy Review Queue
An agent reviews ambiguous comments against your brand's response policy, decides whether to auto-clear, draft a reply for approval, or escalate, and routes its decision…
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.
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.
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.