SOCIAL MEDIA
Escalate negative brand-mention spikes to the comms on-call
Watches a rolling window of social mentions, scores their sentiment, and pages the communications on-call in PagerDuty the moment negative volume breaks past your baseline.
How it runs
The automated pipeline, trigger to output.
- TriggerEvery few minutes (schedule)
- ActionScrape recent brand mentionsApify
- ActionScore sentiment per mentionOpenAI
- LogicNegative share over baseline?
- ActionOpen incident for comms on-callPagerDuty
- OutputPost incident + top mentionsSlack
What it does
It continuously samples public mentions of your brand, classifies each one's sentiment, and compares the share of negative mentions against a rolling baseline. When negativity spikes past your threshold, it opens a PagerDuty incident routed to the comms on-call and drops a summary in Slack so the responder has context before they even open the alert.
When to use it
Use it when your brand is large enough that a bad tweet can snowball overnight and you can't have a human watching the feed at 2am. It's the difference between hearing about a crisis from your CEO and hearing about it from your own alerting.
How it works
- 1A scheduled trigger fires every few minutes.
- 2Apify scrapes recent public mentions across the platforms you track.
- 3OpenAI scores each mention's sentiment and pulls a one-line reason.
- 4A logic step computes the negative share and compares it to the rolling baseline.
- 5If the spike clears the threshold, PagerDuty opens an incident for the comms on-call.
- 6Slack posts the incident link plus the top offending mentions to your war-room channel.
Set it up
What you configure once, before turning it on.
- 1Connect ApifyActors, scrapers, datasets.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 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.