SOCIAL MEDIA
Negative Mention Spike PagerDuty Alert
Watches the rolling volume of negative brand mentions and, when it spikes past your baseline, raises a PagerDuty incident and posts a war-room summary to Slack to catch…
How it runs
The automated pipeline, trigger to output.
- TriggerEvery 10 minutes
- ActionSearch for brand mentionsBrave Search
- ActionCount negatives and summarize themeOpenAI
- LogicOnly continue on volume spike
- ActionTrigger PagerDuty incidentPagerDuty
- OutputPost war-room summary to SlackSlack
What it does
This workflow treats a sudden surge in negative chatter like an outage. It tracks negative-mention volume against a rolling baseline, and when the rate breaks the threshold it pages the comms on-call through PagerDuty and opens a Slack war-room thread summarizing what is being said and where.
When to use it
Use it for crisis detection — a faulty release, a viral complaint, or a PR incident — where minutes matter and you cannot rely on someone happening to watch a feed. It is the early-warning siren, not the everyday triage tool.
How it works
- 1A schedule fires every 10 minutes.
- 2Brave Search pulls the latest mentions.
- 3OpenAI counts negative mentions and summarizes the dominant theme.
- 4A logic step compares the count to the rolling baseline and only continues on a spike.
- 5PagerDuty triggers an incident routed to the comms on-call.
- 6Slack posts a war-room summary with the theme, sample links, and incident link.
Set it up
What you configure once, before turning it on.
- 1Connect Brave SearchWeb, news, image, video search.
- 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.