SOCIAL MEDIA
Log every brand mention to Notion with a daily digest
Captures all public brand mentions into a Notion database tagged by sentiment and platform, then posts a once-a-day summary of volume and mood to Slack.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled scrape of new mentionsApify
- ActionTag sentiment and themeOpenAI
- ActionAppend row to Notion mentions DBNotion
- LogicDaily: aggregate volume and sentiment
- OutputPost daily digest to SlackSlack
What it does
This workflow builds a searchable record of everything said about your brand. Each public mention is written to a Notion database with its sentiment, platform, author, and link, and once a day a digest summarizes total volume and the positive-to-negative split.
When to use it
Use it when you want a durable archive and a trend line rather than real-time pings. Marketing and leadership get a clean Notion table to filter and a morning Slack digest, without anyone watching a live stream of posts.
How it works
- 1A schedule triggers an Apify scrape of new public mentions on a recurring interval.
- 2An OpenAI call tags each mention with sentiment and a short theme.
- 3Each tagged mention is appended as a row in the Notion mentions database.
- 4A second daily schedule reads the day's rows, counts volume and sentiment mix, and asks OpenAI to write a short summary.
- 5The digest posts to a Slack channel for the team to read each morning.
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.
