SOCIAL MEDIA
Broadcast a brand crisis across PagerDuty, Teams, and Discord
When negative mention volume crosses a true crisis threshold, it fans out a single alert simultaneously to the PagerDuty on-call, an MS Teams leadership channel.
How it runs
The automated pipeline, trigger to output.
- TriggerFrequent volume sample (schedule)
- ActionPull recent mention firehoseApify
- ActionScore sentiment and write crisis briefOpenAI
- LogicNegative volume past crisis threshold?
- ActionPage the on-callPagerDuty
- ActionPost leadership briefMicrosoft Teams
- OutputBroadcast to ops roomDiscord
What it does
This is the big-red-button workflow. When negative mentions blow past a crisis-grade threshold — far above the routine spike level — it activates every escalation path at once: it pages the on-call, posts an executive-readable summary to an MS Teams leadership channel, and drops the same brief into a Discord ops room. One trigger, three audiences, no relay delay.
When to use it
Use it for the rare, severe event where minutes of coordination lag cost you. It's deliberately separate from your routine spike alert so it only fires when the situation genuinely warrants pulling leadership and ops together at the same time.
How it works
- 1A scheduled trigger samples mention volume frequently.
- 2Apify pulls the recent mention firehose for your brand.
- 3OpenAI scores sentiment and writes a tight crisis summary with key examples.
- 4A logic step checks whether negative volume crosses the crisis threshold.
- 5If it does, PagerDuty pages the on-call, MS Teams gets the leadership brief, and Discord gets the ops-room broadcast.
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 Microsoft TeamsChannels, chats, files.
- 5Connect DiscordCommunity channels + voice + bots.
- 6Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 7Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 8Test, 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.