Project · Automation

Content pipelines in n8n

Scheduled n8n workflows that find a topic, research it, check the sources and draft an article for WordPress. Built for private publishing sites, so site names are left out.

The problem

News publishing depends on speed, but AI writing without checks can invent facts. The goal was a workflow that could keep up with topics and still refuse to write when the sources were not good enough.

My role

I designed and built the workflows, wrote the prompts, and fixed them as real runs showed problems.

The result

In the runs from 1 to 4 November 2026, about 9 in 10 (88%) ended in a published article. The rest stopped without writing anything: either there was no new topic, or the source check refused it.

About 1 in 5 finished drafts (19%) failed the final checks and was repaired automatically before publishing. None had to be given up.

Scheduled, no manual trigger
Source check before drafting
Failed drafts repaired, not published as is

Figures from the n8n run history, 1 to 4 November 2026.

What I built

  • Topic discovery: a web search step picks a current topic and matches it to the right section of the site.
  • Source check: a topic only moves on if at least two sources load and are not all from one publisher.
  • Claim check: the title and any date it claims must appear on a page the workflow cited.
  • Writing rules: the prompt bans filler and stops research wording leaking into the article.
  • Repair step: if a finished draft fails the final checks, it goes back to be repaired. If it can't be fixed, the run stops and sends an alert instead of publishing.
  • Publishing step: the finished article goes to WordPress with the right category and author.

What I learned

My first source check was too strict and stopped every run. Loosening it safely meant reading the failures one by one, not just lowering the bar. I also learned where automation should stop: one site later moved back to an editor-led process because that served it better.

Proof

The content pipeline in n8n: a 4-hour schedule, topic discovery, a duplicate check, the source check, writing, final checks with a repair branch, then image, WordPress post and cache purge, with an email at each exit.

The workflow in n8n, from the schedule on the left to the published post on the right. Every exit sends an email, so a stopped run is never silent.

Need something like this?

Book a call and tell me what you want to automate.

Book an intro call