Daily brand mention digest in Slack

I want a daily brand mention digest that runs every weekday at 9am Eastern on a cron schedule and posts to Slack. The agent should make the prioritization call so my team opens Slack to a clear set of decisions, not a flat list of mentions.

On each run, use Talkwalker's Search Project operation to pull every mention of my brand from the last 24 hours. Use the project I configure (so my existing topics, filters, channels, panels, and datasets are honored). I'll provide the project ID and the brand query when I set this up. Don't fall back to the global media index.

Once you have the mentions, classify each one into one of four buckets and keep the buckets distinct:

1) Positive coverage worth amplifying. Use these for share-outs, social reposts, or sales enablement. 2) Neutral chatter. Volume context only, no action needed. 3) Negative or risky mentions worth a response. Flag anything that looks like an emerging complaint, criticism, or reputational risk. 4) High-reach mentions regardless of sentiment. Anything with unusually large reach, follower count, or engagement should surface here even if it overlaps another bucket.

Then post a single threaded Slack message using Send a Message to the channel I configure (I'll pass the channel ID or name). Structure it like this:

Parent message: a top-line natural-language summary. Include total volume for the last 24 hours and how that compares to the prior 24 hours (up, down, flat, with the percent change). Include a sentiment split (positive / neutral / negative counts or share). Call out the top 3 stories of the day with one-line framing and direct links. Keep the tone informative, not breathless. End with a short pointer like "Per-bucket breakdown in thread."

Threaded replies: one reply per bucket, in this order: amplify, respond, high-reach, neutral. In each reply, list the mentions as short bullets with the source or author, a one-line excerpt or summary, and a direct link. For the respond bucket, add a brief suggestion of how the team might respond (acknowledge, escalate to support, etc.). If a bucket is empty, post a one-line reply saying so rather than skipping it, so the structure is consistent every day. If a mention qualifies for both high-reach and another bucket, surface it in the more action-oriented bucket and just reference it in high-reach.

Lean on natural-language framing rather than dumping rows. The goal is for someone reading the parent message in 15 seconds to know whether today is a normal day or whether they need to dig into the thread.

If Talkwalker returns zero mentions for the window, still post the parent message with "0 mentions in the last 24 hours" and a one-line reply confirming the digest ran. Don't silently no-op. If Talkwalker errors, post a short Slack message in the same channel saying the digest failed and include the error so I know to investigate.

Configurable inputs I want exposed when I set this up: Talkwalker project ID, brand search query, Slack destination channel, run time and timezone (default weekdays at 9am ET), and the threshold for what counts as high-reach (default to top 10% by reach for the day, with a sensible minimum).