Daily brand reputation monitor

Build me a daily brand reputation monitor as an agent workflow.

Trigger: cron, every weekday at 8:00am in the user's configured timezone.

Inputs the workflow should expose as editable fields: a list of brand keywords (brand names, product names, key executives), the Gmail comms distribution list (To addresses), the Slack channel for urgent alerts (default: #brand-watch), and the on-call PR lead's Slack user ID or handle to tag in alerts.

Step 1. For each keyword on the list, use Bright Data's SERP Search to query Google News scoped to the last 24 hours. Collect the top article URLs (aim for the top 5 per keyword, deduped across keywords).

Step 2. Fan out Bright Data's Scrape URL with Web Unlocker against each unique article URL to fetch clean article text. Skip URLs that fail to return readable content rather than retrying forever.

Step 3. Read every article and for each one produce: a sentiment classification (positive, neutral, or negative), a 30 word summary, 3 to 5 key takeaways, and a reputational importance score that weighs publication reach, sentiment intensity, and whether the article names the user's executives or products. Group articles that cover the same underlying story so the briefing does not repeat itself.

Step 4. Draft a single HTML morning briefing ranked from most to least reputationally important. Use color-coded sentiment labels (green for positive, gray for neutral, red for negative), show the 30 word summary, the key takeaways, the publication name, and a link back to the source article for each entry. Send the briefing with Gmail's Send a Message to the configured comms distribution list. Subject line should include today's date.

Step 5. If any article is classified negative AND has a high importance score, also post a separate Slack alert with Slack's Send a Message to the configured urgent-alerts channel. The alert should tag the on-call PR lead, give a one paragraph summary of what is being said and where, and link to the article. Send one alert per distinct high-impact negative story.

If a day has no notable coverage, still send the morning email so the team knows the monitor ran, and stay silent on Slack.

This is an agent workflow because the value is judgment over which stories matter and how to phrase the briefing, not a fixed pipeline.