用 You.com、Jev 和 n8n 建立晨間 AI 新聞簡報工作流程

This Verified Node Spotlight is a guest post written by Tyler Eastman, Senior Software Engineer at You.com.

The hard part of a news digest was never finding the news.

Searching is cheap and summarizing is cheap. Deciding what's worth reading is the expensive part, because it takes a judgment call on every single item, and a judgment call has always  meant a model call. Run a general-purpose LLM across sixty articles every morning and you're paying real money and real latency to be told that fifty-four of them are reprints of the same press release.

So most digests give up on filtering. They send everything, or they send an LLM summary of everything, which is the same thing with extra steps. Either way the thing arrives in Slack every morning at 8am whether or not anything happened, and within three weeks people stop opening it. A digest that cries wolf daily is worse than no digest.

This workflow filters first. Jev, the first System One model from TypeSafe AI, scores every article that comes back from the search for about four hundredths of a cent each. At that price you can afford to ask three separate questions about every result instead of one vague question about all of them. What survives the filter goes to You.com Research, which writes a short cited brief per topic.

A whole morning costs somewhere between one and four cents. And on a quiet day, when nothing material happened in a topic, the workflow posts nothing at all for that topic. That last behavior is the one that keeps people reading it in month three.

How the brief works

Figure 1: Search wide, filter hard, then spend money only on what survived.

A Schedule Trigger fires every weekday at 8am in your instance's timezone. Config holds your topics, a description of your team, and what that team cares about, so there's one node to edit rather than four.

For each topic, the You.com node searches news from the past day. Anything seen in an earlier run is skipped, so Tuesday's brief doesn't re-report Monday's launch.

Every surviving article goes to Jev, which answers three questions about it in a single call: whether it reports a real development, whether it's actually about the topic, and how much it matters to your team. Articles that clear the materiality threshold continue. The rest are dropped and never cost you anything again.

What's left is grouped by topic, so six outlets covering one model release collapse into one item rather than six. Then You.com Research writes a short brief per topic with linked citations, and Slack posts it.

The order matters. The expensive operation runs last, on a set that's already been cut down by a filter costing a fraction of a cent.

Before you start

• An n8n instance. n8n Cloud and self-hosted both work.
• The You.com node installed. @youdotcom-oss/n8n-nodes-youdotcom is a verified community node. Add a node, type you.com in the search panel, and select it. You can also install it from Settings > Community Nodes > Install using the package name.
• A You.com API key. Sign up here and create a key from the dashboard.
• A TypeSafe API key. Jev is in early access at the time of writing; request access and you'll be brought off the waitlist.
• A Slack credential and a channel your bot has joined.

Try it yourself

Import the free template to your n8n instance to follow along. The canvas loads with every node wired and configured.

Get the workflow

Step 1: Set your topics and what you care about

Open Config. Four things live here.

Your topics. The template ships with model releases, agent tooling, and AI regulation. Three is a good starting number because it keeps the morning post short enough to actually read.

Your team. A sentence or two describing what you build. This is what Jev scores materiality against, and it's doing more work than it looks like. "We ship a developer-facing API for document extraction" and "we run ML infrastructure for a bank" will diverge sharply on the same article about an inference pricing change.

What you care about. The specific things that would change a decision for you: a competitor shipping, a price change, a regulation with a compliance date.

materialityThreshold. How high an article has to score to make the brief. Start where the template has it and adjust after a week of real mornings.

That last one is the dial you'll actually touch. Too high and quiet days go silent in a way that feels broken; too low and you're back to a digest nobody reads. It's one number in one node, which is the point of keeping the judgment criteria in config instead of buried in a prompt.

Step 2: Search the day's news and skip what you've already seen

The You.com node searches each topic over the past day.

Articles that appeared in an earlier run are skipped before anything else happens. Without this, a story that stays in the news cycle for three days shows up in three consecutive briefs, and people learn to skim past the whole message. Deduplication isn't a nice-to-have in a daily digest, it's the difference between a tool and a nuisance.

Figure 2: A single topic returns more than you'd want to read. That's fine, because reading it costs almost nothing.

Search wide here. The filter downstream is cheap enough that returning too many results is not a problem worth optimizing away.

Step 3: Ask Jev three questions about every article

This is the node the rest of the workflow is built around.

Jev isn't a chat model. You hand it a state and a set of typed questions, and it returns typed values with calibrated confidence, in well under a second. It generates no text, which means it also can't generate the wrong shape of text. Here the state is the article, and the three questions are:

Does this report a real development? Separates a launch from a think piece about the launch, a funding round from a roundup mentioning the funding round. This question alone removes most of what a naive digest would have sent you.

Is it about this topic? News search drifts. A query about AI regulation will return a story about a data center zoning dispute, and it isn't wrong exactly, it's just not what you asked for.

How much does this matter to this team? Scored against the team description and priorities from Config. This is the one that produces materialityThreshold.

Figure 3: Three questions, one call, one article. Every question is evaluated independently against the same state.

Three separate questions rather than one combined one is deliberate, and it follows TypeSafe's own guidance on composing atomic questions. Each asks one well-scoped thing, each is evaluated independently and in parallel, and the logic that combines them lives in your workflow where you can see it. Ask instead for a single "should this be in the brief" verdict and you've buried three different judgments inside one number you can't tune separately. When the brief starts surfacing the wrong things, you want to know which of the three questions drifted.

The cost is about $0.00004 per article. Sixty articles across three topics is roughly a quarter of a cent. That number is the entire reason this workflow can filter at all, rather than summarizing everything and calling it filtering.

Step 4: Group by story, not by article

One model release produces coverage in six places by lunchtime. A digest that lists six items for one event is padding, and readers notice.

Material articles are grouped by topic before the brief is written, so multiple outlets covering the same development become a single item with multiple sources behind it. More sources on one story is a signal the story matters, not a reason to take up six lines.

Step 5: Write one cited brief per topic

Only now does anything expensive run. You.com Research takes the surviving articles for a topic and writes a short brief with linked citations, and the result goes to Slack.

Citations are the part that makes this usable in a work context. A brief that asserts a competitor changed their pricing is a rumor; a brief that asserts it with a link is something you can forward to your head of product.

A topic with nothing material gets no post. Not a post saying there was nothing, which is its own kind of noise. Nothing.

Figure 4: Four topics had news. The fifth didn't, so it isn't here.

What it costs

A morning runs about $0.01 to $0.04. That's the whole thing: searches, one Jev call per article, and a research brief per topic that had news. Quiet days cost less, because the research step doesn't run for topics with nothing in them.

The structural reason it's cheap is that the expensive step only ever sees material that already passed a filter costing four thousandth of a cent per item. Invert the order, running the heavy model across everything and asking it to be selective, and you pay for sixty articles' worth of inference to receive four articles' worth of value.

Three things you get that a simpler digest doesn't:

• Silence on quiet days, which is what keeps people opening it in month three.
• A materiality threshold you can tune, rather than a prompt you have to re-litigate every time the output drifts.
• Citations on every claim, so the brief is forwardable.

Where to go from here

Run heavier research on big days. The Research operation has a background mode that returns a task id instead of holding the connection open, paired with a Get Research Task operation you poll until the status comes back completed. Worth adding if you raise the effort level on topics with a lot of material; frontier, the highest effort level, runs this way only.

Add a fourth question. Jev evaluates questions in parallel against the same state, so another one barely moves the response time. An urgency score that promotes a topic to its own immediate message instead of waiting for 8am is a natural next one.

Scope the sources. The You.com search operation takes include_domains, exclude_domains, and boost_domains, up to 500 values each. Boost the outlets you trust without excluding everything else, or exclude a content farm that keeps ranking for your topics.

Pull the full articles. Feed the surviving URLs into the Contents operation with a max_age threshold to fetch and archive the pages themselves. Contents takes multiple URLs in one node.

Change the destination. Slack is in the template because that's where people already are at 8am. Swap in email, a Notion page, or a sheet that accumulates a searchable record of what mattered each day.

Conclusion

Filtering has always been the expensive half of a news digest, which is why most of them don't really filter. What changed is the price of a judgment call. At four hundredths of a cent you can ask three careful questions about every article in the firehose and still spend less on the entire filtering step than on one summary from a frontier model. Search wide, filter hard, then write about only what's left.

Try it now

Import the workflow to drop every node, wired and configured, into your n8n instance.

Get the template

For the full set of operations the You.com node supports, including Answer, Finance Research, and Contents, see the You.com API documentation. For Jev's primitives and how confidence is meant to be used architecturally, see the TypeSafe docs.