Competitive intel monitor from RSS to Notion and Slack

Build me an agent workflow that watches a set of competitor and industry RSS feeds and turns each new article into a structured entry in our Notion competitive intel database, with a Slack ping when the news is high signal.

Trigger: a poll trigger on RSS using the new_item event. The user will provide one or more RSS or Atom feed URLs to watch (competitor blogs, Google News alerts, analyst publications, etc.). Each new feed item fires the agent.

What the agent should do for each new item:

1) Fetch the article body from the link in the RSS item and read it. If only a snippet is available, work from the snippet plus the title.

2) Write a three-bullet summary of what the article actually says, plus a one-sentence 'so what for us' take that explains the implication for our company.

3) Classify the item: identify which competitor it is about (from a list the user supplies, or 'industry' if it is general market news) and assign a topic tag from this set: pricing, product launch, hiring, funding, partnership, other.

4) Dedupe against the Notion intel database. Use Notion's Query a Data Source on the user's competitive intel data source, filtering by the source URL property, to check whether this article has already been filed. If a matching entry exists, stop and do not create a duplicate.

5) If it is new, call Notion's Create a Page as a child of the competitive intel data source. Set structured properties: Title (article headline), Source URL, Published Date, Competitor (select), Topic (select), Summary (the three bullets), and So What (the one-sentence take). Put the full summary content in the page body too.

6) If the topic is pricing, product launch, or funding, call Slack's Send a Message to a channel the user specifies (default suggestion: #competitive-intel). The message should include the headline, the competitor name, the topic, the one-sentence 'so what for us' take, the source link, and a link to the new Notion page. For minor or tangential items (other, hiring, partnership, or low-signal blog posts), skip Slack and just file the Notion entry quietly.

Inputs the user should be prompted for when configuring: the RSS feed URLs to watch, the Notion intel database (data source), the list of competitor names to recognize, the Slack channel for alerts, and which topic tags should trigger a Slack ping (default: pricing, product launch, funding).

Tone: the summary and 'so what' should read like an internal analyst note, concise and specific, no filler.