SOCIAL MEDIA

Brand mention triage: route high-reach posts with draft replies

Scrapes new social mentions of your brand, scores each by author reach and sentiment.

CategorySocial Media
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerScheduled scrape of new brand mentionsApify
  • ActionScore author reach and engagement
  • ActionClassify sentiment and urgencyOpenAI
  • LogicKeep only mentions above reach threshold
  • ActionDraft an on-brand replyOpenAI
  • OutputPost mention, score, and draft to Slack triageSlack

What it does

Watches for new public posts that mention your brand, ranks them by how far they'll travel and how they feel, and pushes only the ones that matter to the right Slack channel with a suggested reply already written. Low-reach noise is filed away silently so the team only sees what needs a human.

When to use it

When your brand gets mentioned across social faster than anyone can read, and you need a single triage queue that surfaces the angry-and-influential posts first instead of making someone scroll a raw firehose.

How it works

  1. 1A scheduled scrape pulls fresh mentions of your brand keywords from social platforms via Apify.
  2. 2Each post's author follower count and engagement are evaluated to compute a reach score.
  3. 3The post text is classified for sentiment and urgency with an LLM.
  4. 4A branch keeps only posts above the reach threshold; everything below is logged and dropped.
  5. 5For qualifying posts the LLM drafts an on-brand reply.
  6. 6The mention, score, and draft reply are posted to the team's Slack triage channel for one-click action.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect ApifyActors, scrapers, datasets.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.