SOCIAL MEDIA
Brand mention triage: escalate viral negative spikes to on-call
Detects sudden surges of negative brand mentions and pages the on-call comms lead via PagerDuty with a context summary before a complaint becomes a crisis.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled scrape of recent mentionsApify
- ActionScore sentiment and compute negative rate
- LogicFire only on negative-spike threshold
- ActionSummarize the incident clusterPerplexity
- OutputOpen PagerDuty incident and page on-callPagerDuty
What it does
Tracks the rolling volume and sentiment of brand mentions and watches for an abnormal spike in negative posts. When a likely PR incident is forming, it pages the on-call communications lead with a tight summary of what's blowing up and where, so a human is engaged in minutes rather than hours.
When to use it
When a single viral complaint or a coordinated pile-on can do real damage and you can't rely on someone happening to refresh a dashboard. This is your early-warning siren for reputational fires.
How it works
- 1A scheduled scrape collects the latest brand mentions across platforms via Apify.
- 2Sentiment is scored and the negative-mention rate is compared against the recent baseline.
- 3A branch fires only when the negative spike exceeds the alert threshold.
- 4Perplexity summarizes the cluster of posts into a plain-language situation brief with likely cause.
- 5A PagerDuty incident is opened and the on-call comms lead is paged with the brief and source links.
Set it up
What you configure once, before turning it on.
- 1Connect ApifyActors, scrapers, datasets.
- 2Connect PerplexitySearch-grounded answers with citations.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, 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.