← All workflows

A CONTENT DESK RUN BY SIX WORKFLOWS.

Blog Agent 1: SEO Strategist

Never argue about what to write next. The data picks the topic.

Starts
Weekly schedule
Size
18 nodes · 18 connections
Tools
Google Search Console, Anthropic Claude, Baserow
Category
SEO & Content · complex
Status
Built and run, currently paused
blog-agent-1-strategist.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

The most expensive content mistake isn't a weak paragraph. It's a whole article nobody searches for. This agent makes topic choice come from a ranked plan and real search data, not from whoever had an idea in Monday's meeting.

Part 2 How it worksWhat it does, step by step

02 · WHAT IT DOES

Once a week it takes the next keyword from your planned backlog, or finds a Google search you're almost ranking for, and turns it into a clear writing brief. It checks you haven't already covered it, then hands the brief to the next agent.

03 · HOW IT RUNS

Step by step, as built.

  1. Take from the backlog

    Fetches the top queued keyword and marks it used straight away, so two runs can never claim it.

  2. Fall back to real data

    With an empty backlog, it pulls Search Console queries ranking in positions 5 to 20, close enough to move up.

  3. Write the brief

    Claude produces the brief; a parse check stops malformed output from moving on.

  4. Skip duplicates

    If a post for this keyword already exists, the run ends without creating another.

04 · TOOLS AND APPS

Built around the systems already in the process.

Google Search ConsoleTrigger or source
Anthropic ClaudeProcessing and orchestration
BaserowDestination or delivery

05 · WHEN SOMETHING BREAKS

Failure is designed in.

  • 4decision points (IF or Switch) check 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.

01Part of 5-agent pipelineProjected
02Zero-touch editorial planningProjected
03GSC-driven topic 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,408163 hours back per year
Full-time equivalent freed
0.1 people
Gross value
$6,528
Running cost
−$120
Return per $1 of running cost
$54.4

The math: 8 post briefs × 120 min × 12 months × 85% ÷ 60 = 163 hours a year × $40/hour = $6,528. Net value = gross value − $120 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