SOCIAL MEDIA
Route Mentions by Sentiment: Thank Fans, Escalate Critics
Splits incoming brand mentions by sentiment so positive ones post to a marketing Slack channel for amplification while angry ones open a Linear issue for human follow-up.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled brand mention scrapeApify
- ActionLabel sentiment and summarizeOpenAI
- LogicBranch: positive vs neutral vs angry
- OutputPositive: post to marketing SlackSlack
- OutputAngry: open Linear issue with threadLinear
What it does
A single pipeline that reads every new mention and sends it down one of two paths. Positive mentions go to a Slack channel where marketing can like, repost, or thank the author. Angry mentions are escalated into Linear with the conversation attached for support to handle.
When to use it
When you want one workflow to cover the full emotional range of mentions, keeping marketing and support each focused on the mentions that are theirs, without two separate listeners drifting out of sync.
How it works
- 1On a schedule, an Apify actor collects new mentions of your brand.
- 2OpenAI labels each mention as positive, neutral, or angry and writes a one-line summary.
- 3A router branches on the label.
- 4Positive mentions post to the marketing Slack channel with the author link for amplification.
- 5Angry mentions create a Linear issue with the full thread and summary for a human to own.
- 6Neutral mentions are logged and dropped to keep both surfaces clean.
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 LinearIssues, projects, cycles, triage.
- 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
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.
Multi-Platform Comment Escalation Router
Ingests inbound comments and replies from your connected social platforms, classifies each for legal or PR risk.
Post-event Discord attendance recap and host digest
After a synced calendar event ends, reconciles who RSVP'd against who actually showed, posts a thank-you recap in Discord, and emails the host a digest of attendance and no-shows.
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…
Carousel render with brand-safety pre-check
Before rendering, an LLM checks the brief copy against brand and policy rules; clean briefs render and archive to S3, flagged briefs route to a review queue instead.
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.