SOCIAL MEDIA
Flag adverse share-of-voice shifts in a Notion exec brief
Compares your brand's sentiment-weighted share of voice against named competitors each week.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly comparison (schedule)
- ActionGather brand + competitor mentionsApify
- ActionScore sentiment and weight SOVOpenAI
- LogicAdverse SOV shift vs prior period?
- ActionDraft exec briefNotion
- OutputNotify leadershipSlack
What it does
This workflow watches not just what people say about you, but how it stacks up against your competitors. Each week it gathers mentions for your brand and a competitor set, scores sentiment, and computes a sentiment-weighted share of voice. When the balance shifts adversely — competitors gaining positive ground while you take on negative — it has an agent compile a Notion brief explaining the drivers and notifies leadership in Slack.
When to use it
Use it for strategic, board-level brand monitoring rather than firefighting. It answers the question execs actually ask: are we winning or losing the conversation versus the people we compete with, and why.
How it works
- 1A weekly scheduled trigger kicks off the comparison.
- 2Apify gathers mentions for your brand and each named competitor.
- 3OpenAI scores sentiment and the engine computes sentiment-weighted share of voice.
- 4A logic step checks for an adverse shift versus the prior period.
- 5If detected, a Paperclip agent drafts a Notion brief analyzing the drivers.
- 6Slack delivers a leadership heads-up linking the brief.
Set it up
What you configure once, before turning it on.
- 1Connect ApifyActors, scrapers, datasets.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect NotionPages, databases, comments.
- 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.