SOCIAL MEDIA
Agent that investigates an angry mention and assigns an owner
Receives a flagged community mention by webhook, has a CEO agent investigate context across your knowledge base and history.
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook delivers a flagged mentionHTTP webhook
- ActionAgent gathers customer and account context
- LogicAgent decides owning team and recommended response
- ActionCreate Linear issue assigning the ownerLinear
- OutputNotify owner in Slack with contextSlack
What it does
Takes a single flagged angry mention delivered by webhook and hands it to an agent that does real triage work: it reads the mention, looks up the customer's history, checks the knowledge base for known issues, decides who should own the response, and notifies that owner with context and a recommended next step.
When to use it
Use this when routing needs judgment, not just a keyword map: a mention might be a billing issue, a known bug, or a misunderstanding, and the right owner depends on context. The agent reasons over it instead of applying a fixed rule.
How it works
- 1A webhook delivers a flagged mention with author, text, and source link.
- 2The agent pulls related customer and account context.
- 3The agent searches the knowledge base for matching known issues or policies.
- 4It decides the owning team and drafts a recommended response.
- 5It assigns ownership by creating a Linear issue for the chosen owner.
- 6It notifies the owner in Slack with the context summary and recommended reply.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, 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.