SOCIAL MEDIA
PR Crisis Comment War-Room Spin-Up
Receives flagged comments via webhook, and when several high-PR-risk comments cluster within a short window.
How it runs
The automated pipeline, trigger to output.
- TriggerFlagged comment received via webhookHTTP webhook
- ActionConfirm PR-risk severity and themeOpenAI
- LogicCheck flagged-comment cluster against crisis threshold
- ActionCreate Slack war-room channel and seed commentsSlack
- OutputOpen crisis-tracking Linear issue and link itLinear
What it does
This workflow listens for already-flagged comments arriving via webhook and detects the difference between one bad comment and the start of a coordinated PR crisis. When high-risk comments cluster within a short window, it stops treating them as individual items and stands up a war room: a dedicated Slack channel for coordination and a Linear issue to track the response.
When to use it
Use it when a viral controversy can form in minutes and you need the comms team assembled in one place fast. It removes the scramble of manually creating a channel, pinging people, and opening a tracker while a story is actively spreading.
How it works
- 1A flagged comment arrives at the webhook endpoint.
- 2An LLM confirms PR-risk severity and theme for the incoming comment.
- 3A logic step checks the recent flagged-comment rate against the crisis threshold within a rolling window.
- 4If the cluster threshold is crossed, a dedicated Slack war-room channel is created and seeded with the offending comments.
- 5A crisis-tracking Linear issue is opened and linked into the new channel for ownership and timeline.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Connect LinearIssues, projects, cycles, triage.
- 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.