SOCIAL MEDIA
Daily Sentiment Digest Routed to Topic Owners
Aggregates the day's brand mentions, computes a sentiment trend by topic, and delivers a tailored digest to each owning team in Slack and Discord highlighting the conversations…
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule after social day close
- ActionPull trailing 24h of mentionsApify
- ActionScore and group mentions into topic trendsOpenAI
- LogicBuild a tailored digest per owning team
- ActionSend internal digests to SlackSlack
- OutputSend community digest to DiscordDiscord
What it does
Replaces the noisy firehose with one calm daily readout per team. It rolls up the day's mentions, breaks sentiment out by topic, and sends each owner only their slice with the items that moved the needle.
When to use it
Use this when individual alerts are too noisy but you still want accountability. It suits leads who want a once-a-day pulse and a short list of mentions worth replying to, split cleanly between teams that live in Slack and teams that live in Discord.
How it works
- 1A daily schedule kicks off the run after the close of the social day.
- 2An Apify actor pulls all mentions from the trailing 24 hours.
- 3OpenAI scores each mention and groups them into topics with a per-topic sentiment trend versus the prior day.
- 4A logic step assembles a separate digest payload for each owning team.
- 5Slack receives the digests for internal teams and Discord receives the community team's digest, each with top movers and recommended replies.
Set it up
What you configure once, before turning it on.
- 1Connect ApifyActors, scrapers, datasets.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Connect DiscordCommunity channels + voice + bots.
- 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
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.