SOCIAL MEDIA
Negative Mention-Spike Escalation to Teams
Detects spikes that are specifically negative or crisis-toned, filters out positive surges, and escalates an evidence pack with severity rating to a Microsoft Teams channel.
How it runs
The automated pipeline, trigger to output.
- TriggerEvery 15 minutes
- ActionCollect mentions, flag volume spikeApify
- LogicScore sentiment, exit if not negative
- LogicCompute severity from volume and reach
- OutputEscalate pack to crisis Teams channelMicrosoft Teams
What it does
Separates good buzz from bad. A spike from a viral fan moment shouldn't page the crisis team — a spike of complaints or backlash should. This workflow only escalates when the surge is meaningfully negative, and grades how urgent it is.
When to use it
Use this when your comms or risk team only wants to be pulled in for reputation threats, not every uptick. Ideal for orgs running incident response in Microsoft Teams who need signal, not noise.
How it works
- 1A schedule fires every 15 minutes.
- 2Apify collects recent mentions and the spike check flags above-baseline volume.
- 3A logic step scores sentiment across the spiking posts and exits if the surge is neutral or positive.
- 4For negative spikes, a severity rating is computed from volume, negativity, and author reach.
- 5The top negative posts plus the severity rating are assembled into an escalation pack.
- 6The pack is posted to the crisis-response Microsoft Teams channel, with high-severity events flagged for immediate attention.
Set it up
What you configure once, before turning it on.
- 1Connect ApifyActors, scrapers, datasets.
- 2Connect Microsoft TeamsChannels, chats, files.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.