← All workflows

A CONTENT DESK RUN BY SIX WORKFLOWS.

Blog Agent 2: Deep Researcher

Every article starts from real sources, not a model's best guess.

Starts
Polls every 10 minutes
Size
10 nodes · 9 connections
Tools
Exa, Baserow
Category
AI Agents · complex
Status
Built and run, currently paused
blog-agent-2-researcher.jsonn8n canvas

Drawn by n8n's own canvas from the workflow file, synced 2026-09-29. Click it to pan and zoom. Node settings, credentials, prompts and IDs are removed; names, layout and wiring are exactly as built.

Part 1 The problemWhy teams need this

01 · THE PROBLEM

AI that writes without sources fills the gaps with confident nonsense, and that's what gets a brand embarrassed. Doing the research as its own step means every draft is built on material that actually exists.

Part 2 How it worksWhat it does, step by step

02 · WHAT IT DOES

It picks up a new brief, locks it so nothing else touches it, and searches the web for credible sources on the topic. The research is attached to the post for the writer. If the search fails, the post is flagged instead of moving on half-empty.

03 · HOW IT RUNS

Step by step, as built.

  1. Find work

    Fetches one post waiting for research. No work, and the run ends quietly.

  2. Lock it

    Marks the record as in progress before doing anything slow.

  3. Search

    Exa returns sources for the topic, which are assembled into a research brief.

  4. Save or fail loudly

    Research is written back to the record; an Exa failure routes to an error status.

04 · TOOLS AND APPS

Built around the systems already in the process.

ExaTrigger or source
BaserowDestination or delivery

05 · WHEN SOMETHING BREAKS

Failure is designed in.

  • 1node has its own error branch, so a failure is routed and handled, not just logged.
  • 1decision point (IF or Switch) checks the data before it moves on.
  • ✓Anything unhandled triggers our central error workflow, so a crash gets reported instead of failing silently.

Standard on every build

  • Schema validation before downstream writes
  • Retry and error routes for external API failures
  • Duplicate-safe processing and idempotent updates
  • Human approval where the action carries business risk
  • Execution logging for support and audit review

Part 3 The impactWhat it's worth, and how we'd build yours

06 · PROJECTED IMPACT

What it should change in the business.

018–12 sources per articleProjected
02Auto citation extractionProjected
03Source quality scoringProjected

Projections for a typical deployment. The calculation below shows the math, and you can put in your own numbers.

07 · ROI CALCULATION

How it pays back in your business.

The starting numbers are a hypothetical deployment sized to the projections above. Change any of them to your own volumes and costs, and the math updates underneath.

Projected net value per year$6,348163 hours back per year
Full-time equivalent freed
0.1 people
Gross value
$6,528
Running cost
−$180
Return per $1 of running cost
$36.3

The math: 8 posts researched × 120 min × 12 months × 85% ÷ 60 = 163 hours a year × $40/hour = $6,528. Net value = gross value − $180 running cost a year.

08 · HOW WE'D BUILD YOURS

How we'd build yours.

  1. Discover: map the current process, systems, volumes, owners and exceptions.
  2. Design: define the canonical data model, approvals, retries and system boundaries.
  3. Build: implement credentials, nodes, validation and observable error routes.
  4. Prove: run controlled data through success, duplicate and failure scenarios.
  5. Operate: publish runbooks, ownership and measurable service levels.

SAME SYSTEM

A content desk run by six workflows.

Five agents hand a blog post down a line, each one polling for work in its own state and passing it on: keyword, research, copy, cover image, publish. A sixth drafts the weekly newsletter and waits for approval by email.

YOUR VERSION

Want this, wired to your tools?

Tell us what the process looks like today: the systems, the volumes, the step everyone hates. We'll come back with the n8n version and where a person stays in charge.

Start a project Back to all workflows