← All workflows

A CONTENT DESK RUN BY SIX WORKFLOWS.

Blog Agent 4: Image Designer

On-brand cover images for every post, without briefing a designer.

Starts
Polls every 5 minutes
Size
14 nodes · 15 connections
Tools
Anthropic Claude, OpenAI, Sanity, Baserow
Category
AI Agents · complex
Status
Built and run, currently paused
blog-agent-4-designer.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

Cover images are small work that quietly holds up publishing. And when they're made one-off, a 150-post blog ends up looking like 150 different companies. One fixed style in the prompt keeps it looking like yours.

Part 2 How it worksWhat it does, step by step

02 · WHAT IT DOES

For every finished draft it writes an image brief in your house style, generates the cover, and uploads it straight to your CMS. If the image fails, the post still moves on without one rather than holding up the whole line.

03 · HOW IT RUNS

Step by step, as built.

  1. Find and lock

    Picks up one post whose copy is written.

  2. Brief the image

    Claude turns the article into an image prompt within the house style.

  3. Generate and upload

    OpenAI generates the image; it is converted to a file and uploaded to Sanity.

  4. Degrade gracefully

    Separate branches save the post with or without an image, so a failed image never stalls the pipeline.

04 · TOOLS AND APPS

Built around the systems already in the process.

Anthropic ClaudeTrigger or source
OpenAIProcessing and orchestration
SanityProcessing and orchestration
BaserowDestination or delivery

05 · WHEN SOMETHING BREAKS

Failure is designed in.

  • 4nodes have their 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.

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.

01Auto hero image generationProjected
02Brand-consistent stylingProjected
03Web-optimised outputProjected

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$3,33686 hours back per year
Full-time equivalent freed
0 people
Gross value
$3,456
Running cost
−$120
Return per $1 of running cost
$28.8

The math: 8 cover images × 60 min × 12 months × 90% ÷ 60 = 86 hours a year × $40/hour = $3,456. 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