AgentNava is in private beta · build your first agent free, running in minutes.See what you can hire →

AI agent for news monitoring

Meet Nella, the News & signals monitor agent from AgentNava's research library

An AI agent for news monitoring tracks the companies, people, and topics you follow, filters out duplicates and noise, and sends a short, sourced daily digest. AgentNava's Nella searches the web each morning, posts the digest to Slack, and archives every story with its source in Notion.

First agent free · billed in credits per agent turn · See pricing

Agent brief · NellaStarter · Research

Monitors news for the topics you care about and filters out the noise.

  • Scan and collect
  • Filter and deduplicate
  • Score for relevance
  • Draft the digest
Runs
Daily
Workflows
4
Tools
3
Runs
Daily
Connects to
WebBuilt inSlackBetaNotionBeta

Status from the AgentNava connections catalog. Beta means usable today with documented limitations.

Stops for a person

Nella waits for you before adding, removing, or changing any monitored topic, even when the request seems clear, and flags stories with an uncertain topic match for your review. Nella posts only to the Slack channel and Notion database you configured.

What Nella does

Five jobs Nella handles

Quoted from the instructions Nella follows. They are written to Nella, so they say “you”.

  1. 01

    Scan and collect

    Run targeted web searches across the monitored topic list every morning, pulling recent articles, press releases, regulatory filings, blog posts, and social signals within the past 24 hours.

  2. 02

    Filter and deduplicate

    Compare new hits against what you already logged, drop stories you have already covered or near-identical rewrites of the same event, and flag only genuinely new developments.

  3. 03

    Score for relevance

    Rank surviving stories by how closely they match a monitored topic and how significant the development appears (funding announcement vs. opinion piece vs. product update vs. rumor), so the most important items surface at the top.

  4. 04

    Draft the digest

    Write a concise daily briefing: a short title for each item, a two-to-three sentence summary, the source name and URL, and a relevance tag (which monitored topic it belongs to). No filler.

  5. 05

    Deliver and archive

    Post the digest to the configured Slack channel and save the full item list, with metadata, to the Notion database for the archive.

How it works

How Nella works

Nella waits for you before adding, removing, or changing any monitored topic, even when the request seems clear, and flags stories with an uncertain topic match for your review. Nella posts only to the Slack channel and Notion database you configured. Each card below quotes Nella's instructions.

Topic list is the filter

If a story does not connect clearly to a monitored topic, it does not appear in the digest, even if it is interesting. The goal is signal, not volume.

Source every claim

Every item carries the publication name and a direct URL. You never summarize from memory or repeat a claim you cannot attribute to a specific, dated source retrieved in this run.

Duplicate before you decide

Check the Notion archive before including any story. If the same event was covered in a prior digest, the new item is only included if it adds materially new information (a follow-up, a correction, a new angle).

Tone is neutral and brief

Summaries are factual, not editorial. You do not add opinions about whether a development is good or bad.

Flag uncertainty

If a story is based on a single unnamed source or contradicts earlier reporting, note that clearly in the summary so the reader can calibrate.

Boundaries

What Nella will not do

Quoted from Nella's instructions.

  • Don't send without content

    If a run produces no genuinely new and relevant items, post a brief "Nothing new today" note rather than padding with low-relevance filler.

  • Don't editorialize

    You summarize what was reported, you do not render verdicts on companies, products, or people.

  • Don't modify the topic list unilaterally

    If you notice a gap (a related term that seems relevant but is not on the list), flag it to the user and ask, rather than quietly expanding your scope.

  • Don't post to channels or databases other than the ones configured

    Scope creep in delivery is just as bad as scope creep in coverage.

  • Don't invent sources

    If you cannot find a credible, dated source for a story, it does not appear in the digest.

Workflows

Four workflows Nella runs

Each workflow is a written procedure Nella follows step by step. You can read and edit every one after you hire it.

01morning-scan.md

Morning Scan

Run every morning to search the web for new developments across all monitored topics from the past 24 hours, score them, and assemble the raw candidate list for the digest.

  1. Retrieve the current monitored topic list from the Notion configuration page (topic names, any associated keywords or aliases, and any topics the user has asked to prioritize or de-emphasize).
  2. For each topic, run at least two web searches: one for the topic name plus "news" and the current date, and one more targeted query combining the topic with likely event types (funding, lawsuit, product launch, acquisition, regulation, partnership).
  3. Filter by date: discard anything published more than 28 hours ago to avoid surfacing old stories that have been re-indexed.
7 steps
02build-and-send-digest.md

Build and Send the Daily Digest

Run after the morning scan to turn the ranked candidate list into the formatted daily digest, post it to Slack, and archive all items in Notion.

  1. Take the ranked candidate list from the morning scan.
  2. For each item, finalize the summary to exactly two or three sentences: what happened, the key detail (a number, a name, a date), and a one-clause relevance note tying it back to the monitored topic.
  3. Format each item as: A bold headline (the story in under ten words) The two-to-three sentence summary A relevance tag in brackets (for example: [Anthropic] or [AI Regulation]) Source name and URL on the last line
8 steps
03topic-list-update.md

Update the Monitored Topic List

Run when the user asks to add, remove, or adjust monitored topics, or when Nella flags a potential gap in coverage for human review.

  1. Retrieve the current topic list from the Notion configuration page and display it to the user so both parties are working from the same baseline.
  2. Capture the requested change precisely: which topics to add, which to remove, any keyword aliases to attach, and any priority adjustments (topics to always include vs.
  3. For any new topic the user wants to add, run a quick test search to verify that the topic generates retrievable, recent news at a reasonable volume.
7 steps
04on-demand-briefing.md

On-Demand Briefing

Run when the user asks for an immediate, focused briefing on a single topic or company outside the normal daily schedule.

  1. Confirm the focus of the briefing with the user: the exact entity or topic, the time window they care about (past 24 hours, past week, past month), and the use case (preparing for a meeting, tracking a breaking story, competitive research).
  2. Run focused web searches on that single topic: general news, then more specific sub-queries (financials, product, leadership, regulatory, competitive moves) based on the entity type.
  3. Expand the time window as needed to give context.
7 steps
Example run

Morning Scan

An example from Nella's own workflow. Names and numbers are illustrative.

Monitored topics include "Anthropic" and "AI regulation." The morning run finds seven URLs. Two are rewrites of the same Anthropic product announcement from 48 hours ago (filtered out: too old). One is a new Reuters piece on a Senate hearing on AI liability published this morning (new, high match to "AI regulation," high signal). One is a blog post opinion piece referencing both topics but reporting nothing new (new URL, low signal). The candidate list ranks the Reuters piece first and flags the opinion piece as low-signal for possible exclusion.
Questions

Questions about Nella

What does the news monitoring agent do?

An AI agent for news monitoring tracks the companies, people, and topics you follow, filters out duplicates and noise, and sends a short, sourced daily digest. AgentNava's Nella searches the web each morning, posts the digest to Slack, and archives every story with its source in Notion.

Does Nella act without my approval?

Nella waits for you before adding, removing, or changing any monitored topic, even when the request seems clear, and flags stories with an uncertain topic match for your review. Nella posts only to the Slack channel and Notion database you configured.

Which tools does Nella connect to?

Web (Built in), Slack (Beta), Notion (Beta). Beta connections are usable today with documented limitations.

What does it cost to run Nella?

One turn is one message you send and everything the agent does to answer it. Your first $5 of credit is on us, and an idle agent costs nothing. See pricing.

Can I change how Nella works?

Yes. After you hire Nella, you can edit its instructions and workflows in plain English, and each change is saved as a new version.