Weekday competitor news digest in Slack with Tavily

Build an agent workflow that runs every weekday at 8am ET and posts a competitive intelligence digest to Slack.

Trigger: cron, weekdays only, 8am America/New_York.

User-configurable inputs the workflow should expose:

1) A list of competitors (company names, with optional homepage URLs to help disambiguate). 2) The lookback window for news, defaulting to the past 7 days. 3) The target Slack channel where the digest should be posted.

For each competitor in the list, use the Tavily Search operation with search_depth set to advanced and time_range set to week. Run focused queries that cover the five news categories we care about: product launches, pricing changes, leadership moves (hires, departures, promotions of execs), partnership announcements, and funding news. It is fine to issue more than one Tavily search per competitor if a single query does not cleanly cover all five categories. Embed the competitor name (and homepage domain if provided) in the query so results are about that company specifically, not generic industry news.

Collect the results across all competitors. Deduplicate items that point to the same story (same URL, or near-identical title). For each item, write a single one-line summary in plain English and keep the source URL.

Group the surviving items by competitor and rank them so the most material news (funding, launches, leadership changes) floats to the top. Cap the entire digest at roughly 10 bullets total across all competitors. If a competitor has no notable items this week, omit that competitor from the digest rather than printing a 'no news' placeholder.

If the deduped, ranked list is empty across every competitor, do not post anything. Skipping the post on slow days is required, not optional. Do not send an empty digest.

Otherwise, format the digest as a Slack message with a short header (date and a one-line framing like 'Competitor news, past 7 days') followed by competitor sub-headings, each with their bulleted one-liners. Each bullet should include the source link inline. Then call the Slack Bot Send a Message operation to post it to the configured channel.

Use the Slack Bot integration (xoxb bot token), not the user OAuth Slack integration, because this is an automated digest that should be attributed to a bot.

Additional information

What does this prompt do?

Watches each competitor in your list for the past week and pulls fresh news across product launches, pricing changes, leadership moves, partnerships, and funding.
Groups the findings by competitor and writes a one-line summary of each item with a source link.
Posts a single, capped digest to your marketing or strategy channel in Slack, and stays quiet on slow news days instead of sending an empty digest.

What do I need to use this?

A list of competitor names or homepage URLs you want to watch.
A Tavily account so we can run real-time web searches. The free tier is enough to get started.
A Slack workspace and the channel where the digest should land.

How can I customize it?

Swap competitors in and out at any time, or run separate digests for different markets or segments.
Change the schedule (daily, twice a week, Mondays only) or shift it to your local time zone.
Tighten or widen the news categories. For example, drop hiring news, or add analyst coverage and conference talks.

Frequently asked questions

What kinds of competitor news does this surface?

Product launches, pricing changes, leadership moves, partnership announcements, and funding news from the past week. You can tune the categories to match what your team actually cares about.

What happens on a slow news day with nothing new?

It skips the post instead of sending an empty digest, so your Slack channel stays useful and never feels noisy.

Can I track more than ten competitors?

Yes. The digest itself is capped at around ten bullets so it stays scannable, but you can add as many competitors as you want. The workflow simply picks the most notable items across the full list.

Will the digest show me where each item came from?

Yes. Every bullet includes a link back to the original article or announcement so anyone on the team can click through and read the source.

Does it post as a bot or as me?

It posts from a Slack bot in your workspace, not from your personal account, so the digest looks like an automation rather than a message you wrote.