SOCIAL MEDIA
Sentiment incident war-room opener
When a pile-on crosses a hard severity bar, it opens a Notion incident page seeded with the context pack, pages the comms owner via PagerDuty, and posts the war-room link to Slack.
How it runs
The automated pipeline, trigger to output.
- TriggerEscalation webhook from detectorHTTP webhook
- LogicSeverity at or above war-room bar?
- ActionCreate seeded Notion incident pageNotion
- ActionRaise PagerDuty page to on-call commsPagerDuty
- OutputPost war-room link to SlackSlack
What it does
Turns a confirmed community blow-up into a managed incident. When sentiment escalation passes a hard severity bar, it spins up a Notion war-room page pre-filled with the timeline and quotes, raises a PagerDuty page so the comms owner gets woken up, and drops the war-room link into Slack so everyone coordinates in one place.
When to use it
Use this for the rare-but-serious events where a holding tweet is not enough and you need a tracked incident with an owner, a timeline, and a single source of truth.
How it works
- 1An upstream escalation webhook fires when a detector confirms a high-severity pile-on.
- 2A logic step confirms severity is at or above the war-room bar.
- 3A Notion incident page is created, seeded with the triggering context, timeline, and source quotes.
- 4PagerDuty raises a page to the on-call comms owner.
- 5The Notion war-room link and severity summary are posted to the Slack incident channel.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect NotionPages, databases, comments.
- 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.