Specialist publisher, family-run
We automated newsletter drafts for a publisher
A family-run specialist publisher wanted to adapt existing articles for newsletters and other formats while editors remained responsible for every publication.
| Industry | Media & Publishing |
|---|---|
| Services | AI Agents, n8n Automation |
Format changes consumed editorial time
An approved article became newsletter teasers, short summaries and variants for different reader groups. Editors copied text between tools, shortened passages and added links. After a correction, they had to find the derived versions individually.
The publisher had already experimented with language models. The drafts read well, but occasionally changed an article’s meaning or omitted qualifications. Without a visible connection to the source, editors had to check every sentence again. This did little to make the review itself easier.
Every draft had to remain verifiable against its source
Our task was to automate the path from an approved article to an editorially reviewed format draft. Editors defined tone, audience and the limits of condensation. The workflow would adapt existing content and make deviations easy to find. Publication and distribution remained subject to explicit approval by the responsible editors.
The pipeline linked format rules to source versions
Only approved articles entered the workflow
The n8n workflow retrieved content from the designated editorial collection. Drafts and blocked articles did not enter automated processing.
Format profiles guided adaptation
Editors maintained rules for newsletters, teasers and summaries. These described reader interests, tone and permitted treatment of quotations.
Drafts retained their source references
Each variant linked to the article and its source version. The review interface placed source text and draft side by side so editors could judge cuts in context.
Changes required renewed approval
When a source changed, the workflow flagged affected variants for another review. Approval applied only to the specific draft reviewed.
Editors tested passages that were difficult to shorten
We worked with editors, the audience team and the publisher’s technical support staff. Editors selected articles whose meaning could easily shift when shortened. These included texts with conditions, indirect quotations and technical qualifications. Our recurring reviews focused on those passages.
A freely written summary was quicker to generate but required more review. We therefore narrowed the task of each model step. The pipeline first selected relevant statements with source references, then derived the format draft from them. Editors could inspect both stages and correct misplaced emphasis.
For distribution, we connected the workflow to the existing approval process. Missing sources or technical errors stopped processing and routed the case to the responsible team. Editors could also write a variant entirely themselves. In working sessions, we used their corrections to improve specific format rules.
Editors reviewed format variants in context
Newsletters and other format variants entered editorial work as prepared drafts. Sources and approval status were directly visible. After corrections to the original article, the team could update affected variants selectively. Editors retained control over selection, wording and distribution and had less content to move between repositories.
Source versions belong in editorial approval
Shortening needs difficult test articles
Test formats on articles with qualifications and quotations. Straightforward news items reveal little about a drafting process’s limits.
Format rules need an editorial owner
Name someone who turns recurring corrections into specific changes to the rules.
Source corrections must reach derived versions
A pipeline needs a way to resubmit derived texts for review after changes.
A first conversation takes 30 minutes.
We look at which format changes in your editorial team could start with traceable drafts.