SOCIAL MEDIA
Page on-call when negative mentions spike
Watches the rolling rate of negative brand mentions and, when it crosses a threshold that signals a brewing PR crisis, triggers a PagerDuty incident and posts a war-room thread…
How it runs
The automated pipeline, trigger to output.
- TriggerFrequent scheduled mention scrapeApify
- ActionLabel sentiment and count negativesOpenAI
- LogicTrigger only when negative rate spikes
- ActionOpen PagerDuty incidentPagerDuty
- OutputOpen Slack war-room thread for commsSlack
What it does
This workflow is an early-warning system for reputation crises. It tracks how many negative mentions arrive per interval, and when the rate jumps abnormally it pages the on-call comms owner and opens a coordination thread before the situation snowballs.
When to use it
Use it when a single bad post is fine but a sudden surge is an emergency: an outage, a viral complaint, or a bad headline. Routine routing misses velocity; this catches the spike specifically and treats it like an incident.
How it works
- 1A schedule triggers an Apify scrape of recent mentions every few minutes.
- 2An OpenAI call labels each mention's sentiment, then the workflow counts negatives in the current window.
- 3A branch compares the negative count against a baseline threshold and only proceeds on a spike.
- 4A PagerDuty incident is created with the count, sample posts, and links.
- 5A Slack message opens a war-room thread tagging the comms team so response can coordinate.
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
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.