Content repurposing with n8n: one piece of content, a week of posts

The math of content marketing: writing takes hours, distribution takes minutes — but only if the distribution is systematized. Here is the exact n8n pipeline that turns one piece of content into a week of posts without you touching a calendar.

The problem with manual repurposing

Most creators write one piece of content and stop. The distribution checklist — post it on X, rework it for LinkedIn, send it as a newsletter, follow up in three days — is the highest-leverage hour of the week, and it is also the first thing that gets dropped when work piles up. Repurposing dies because it depends on memory and discipline. Automation removes both requirements.

Workflow 1 — Turn feeds into digests

You read five newsletters and feeds to stay sharp. That is thirty minutes of scanning per day. Instead, an n8n workflow fetches the RSS feeds you care about every six hours, asks an AI model to summarize each new item in two sentences plus a headline, and emails you one digest with everything worth reading.

The chain is simple: Schedule Trigger → HTTP Request (fetch RSS) → Split Out → AI summarize → filter empties → merge → email digest. One config node holds the feed URLs, so adding a source is editing a single field. You stop checking feeds entirely — the digest arrives and you read for three minutes.

Workflow 2 — Rewrite for each platform

Every platform has a different native format, and readers punish you for cross-posting the same text. X wants 280 characters and a punchy take. LinkedIn wants a hook, four short paragraphs, and a call to action. Email wants a subject line that survives the inbox.

The converter workflow takes this friction to zero:

curl -X POST https://your-n8n/webhook/convert \
  -H "Content-Type: application/json" \
  -d '{"content":"your long article or thread...", "platform":"x"}'

You send long content in, and the AI rewrite for the platform you asked for arrives in your inbox. Send the same content three times with a different platform value and you have X, LinkedIn, and email versions in under a minute, each in native format.

Workflow 3 — Queue the publishing

Writing on the right day but publishing only once is leaving reach on the table. A publish queue workflow starts from a single webhook call with your content and runs a reminder cadence: immediate confirmation, then a nudge at 6 hours, 24 hours, and 72 hours with the text ready to paste. You post when the reminder lands — the queue never forgets, never skips, and runs for every piece of content in parallel.

What this saves, in numbers

A realistic week: three pieces of content, three platforms each, two follow-up slots each. That is roughly 30 manual steps of copy-paste-adapt-schedule. The three workflows collapse it to: paste content into three webhook calls. The only work left is the part only you can do — deciding what to say.

If you would rather import the complete, tested version of this pipeline instead of building it node by node, the pack below ships exactly these three workflows with a setup guide.