Skip to content
ENGINEERING / PHOTOGRAPHY
日本語
ENGINEERING / PHOTOGRAPHY
日本語 LinkedIn GitHub

Case 06 · Automation · Content

SEO content pipeline

Writing is one step. Reviewing it and acting on the review are two more. So the loop runs itself.

Role
Design and build
Built with
n8n (self-hosted) · Google Sheets · Google Docs · Apps Script
Interface
A menu in the spreadsheet already in use
All work

Interface A menu in the spreadsheet already in use

  1. Run from a keyword, a product and a situation, produce an article and its images, create the Doc, write the link back to the sheet.
  2. Review read what was produced and name three things that could be better.
  3. Optimise act on that review and append the result to the same Doc.
Process diagram, not a screenshot: the three actions as the text below describes them.

01Three actions, one loop

Run: from a keyword, a product and a situation, produce an article and its images, create the Doc, write the link back to the sheet. Review: read what was produced and name three things that could be better. Optimise: act on that review and append the result to the same Doc.

02Why a spreadsheet

The work already lived in a Google Sheet. Putting the controls in a menu at the top of that sheet meant nobody had to learn a new tool, and the row stays the record of what happened to it.

03Self-hosted on purpose

n8n runs on Zeabur rather than a managed plan, so the credentials and the drafts stay where they can be accounted for.

3
actions: run, review, optimise
4
workflows
1800
words minimum per article