2026Automation
Dro3 Tech editorial pipeline
An n8n chain that turns an RSS watch into WordPress articles, with mandatory human review before anything goes live.

- Context
- Client engagement. An Arabic-language technology news site has to publish several times a week to stay visible in search. Doing it by hand is a full-time job: monitoring, triage, writing, illustrating, publishing.
- Problem
- Automating publication without automating mistakes. A pipeline left to itself eventually republishes a topic it already covered, or publishes something nobody read. Both cost more than the time they save.
- Approach
- It pulls four RSS feeds together, then checks for duplicates twice. An in-memory cache goes first because it is free and instant; anything that slips past it is checked against the WordPress API, which has the final say. Gemini 2.5 Pro writes the article, Gemini Flash generates the cover image, the media is uploaded to WordPress. Then the chain stops: a Telegram notification and a webhook wait.
- Outcome
- Three outcomes behind the human go-ahead: publish, archive as a draft, or cancel. Cancelling deletes the uploaded image so no orphan media accumulates. 130 articles published so far, roughly one every two days.
- My role
- Designed and built, for a client.
- Stack
- n8n
- Gemini 2.5 Pro
- WordPress REST API
- Telegram Bot API
- RSS
- Repository
- last commit September 2026
Sanitised release
The workflow is published with the tokens replaced by environment variables and the client's details removed.
Live