SOCIAL MEDIA
Negative Brand-Mention Spike to Linear with Context
Scrapes fresh brand mentions across social platforms, scores sentiment, and when negative mentions spike above your baseline it opens a Linear issue pre-filled with the offending…
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled scrape of brand mentionsApify
- ActionScore sentiment per mention with OpenAIOpenAI
- LogicContinue only if negative rate exceeds baseline
- ActionSummarize root cause and pick owning teamOpenAI
- OutputOpen Linear issue with quoted posts and ownerLinear
What it does
Watches public conversation about your brand and turns a sudden surge of negative sentiment into a single, actionable Linear issue so it lands with the right team instead of getting lost in a notification feed.
When to use it
Run this when you need an early-warning system for reputation problems — a botched release, a viral complaint, a pricing change gone sideways. It only fires when negativity actually spikes, so your team isn't paged for routine grumbling.
How it works
- 1On a schedule, an Apify actor scrapes recent public mentions of your brand handles and keywords.
- 2Each mention is sent to OpenAI for a sentiment score and a one-line reason.
- 3A logic step compares the rolling negative-mention rate against your stored baseline; if it clears the spike threshold, the flow continues, otherwise it exits quietly.
- 4OpenAI clusters the negative posts into a short root-cause summary and picks the most likely owning team (product, support, or trust).
- 5A Linear issue is created with the summary, the worst three quoted posts, the sentiment delta, and the suggested assignee.
Set it up
What you configure once, before turning it on.
- 1Connect ApifyActors, scrapers, datasets.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect LinearIssues, projects, cycles, triage.
- 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.