SOCIAL MEDIA
Open a Slack war-room thread for high-reach negative mentions
When a negative mention comes from a high-follower or high-engagement account, it instantly spins up a dedicated Slack thread with the post, the account's reach.
How it runs
The automated pipeline, trigger to output.
- TriggerNew mention webhookHTTP webhook
- ActionEnrich author reach and velocityApify
- ActionConfirm sentiment and draft replyOpenAI
- LogicNegative AND high reach?
- OutputOpen war-room thread with pingSlack
What it does
Not every negative mention matters equally. This workflow filters incoming mentions for sentiment AND reach, so a complaint from an account with a large following or fast-rising engagement triggers an immediate response while a no-name gripe doesn't. It opens a focused Slack thread containing the post, the account's reach signals, an AI-drafted reply for a human to approve, and a ping to the on-shift team.
When to use it
Use it when virality risk, not raw volume, is your worry — a journalist, creator, or competitor with a big megaphone posting something damaging. You want eyes on it in minutes, not in tomorrow's digest.
How it works
- 1A webhook trigger receives new mentions as your listening tool detects them.
- 2Apify enriches the mention with the author's follower count and engagement velocity.
- 3OpenAI confirms the sentiment is negative and drafts a candidate reply.
- 4A logic step gates on both negative sentiment and a reach threshold.
- 5Slack opens a war-room thread with the post, reach data, draft reply, and an @here ping.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 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
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.