Content repurposing and social drafts with n8n

#01Why automate repurposing?

Most teams publish a post and promote it once. The same piece could feed a week of social posts, a newsletter section and FAQ content that AI assistants can quote. Doing that by hand is tedious, so it doesn't happen. Automation makes the default "drafts exist", and the social manager's job becomes editing rather than starting from a blank page.

#02Getting clean source text

Models work better on clean text. Options, from simplest:

1. The feed's content field, if your feed includes full content.
2. HTTP Request plus the HTML node to extract the article body by CSS selector.
3. Your CMS API, which often returns structured content.

Strip navigation, footers and related-post blocks. Long posts may need trimming to a sensible length; for most posts, the model can handle the whole article.

#03Prompting for platform-native drafts

Generic "summarise for LinkedIn" prompts produce generic posts. Better instructions:

• Give the audience and the single idea for each format.
• Ban phrases your team dislikes.
• Include two example posts your team wrote and liked.
• Ask for one specific detail from the article in each post, so drafts aren't vague.
• Limit length explicitly.

The Claude track's content repurposing lesson has prompts you can paste in.

#04FAQ drafts and AI visibility

FAQ-style content answering real buyer questions is useful on your site and can help AI assistants quote you accurately. The repurposing workflow can draft three to five questions and answers per post for your content team to review and place. Measuring whether that helps is lesson 12's job.

Our view: repurposing workflows pay back quickly because the inputs are already approved content. The risk is lower than drafting new claims from scratch.

#05Formats to generate from one piece

Generate a structured JSON object with one field per format. A single model call is cheaper than one per format, and an IF node can skip formats you don't need.

#06Picking up new content automatically

The RSS Feed Trigger starts a workflow when your blog's feed has new entries. If your CMS has no feed, a Schedule Trigger plus HTTP Request against your sitemap or CMS API works. Use Remove Duplicates with "Remove Items Processed in Previous Executions" on the URL so the same post isn't repurposed twice.

#07Scheduling posts

Some social tools have n8n nodes or APIs, and the LinkedIn and X nodes can post. Our advice: write drafts to a sheet or your social tool's draft queue, and let a person schedule. Social posts go to the public under your brand name, and AI tone mistakes are visible.

#08Prompt structure for repurposing

A reliable structure for the single structured call:

1. Role: "You write social and email copy for a B2B software brand."
2. Source: the cleaned article text and its URL.
3. Audience and voice rules.
4. Per-format instructions: length, hook style, one specific detail, CTA.
5. Two example posts your team liked.
6. Output: JSON with one field per format.

#09Handling edge cases

Track which drafts get used. Formats nobody uses are cost without value.

#10The repurposing workflow, node by node

The parser's JSON example:

{
  "linkedin": "post text",
  "newsletter": "two sentences",
  "sales_snippet": "three sentences",
  "faq": [{ "q": "question", "a": "answer" }]
}

#11Cost math for this workflow

On a polling trigger, executions depend on whether the trigger fires only when new items appear. The RSS Feed Trigger starts a workflow execution when it finds new items, so a blog with eight posts a month uses about eight executions plus any failed runs. Model calls are one per post, because all formats come from one structured call. That is far cheaper than four separate calls per post.

#12Edge cases you will meet

• Feed shows a summary only. The HTTP Request and HTML steps fetch the full article. If your site blocks bots, use the CMS API instead.
• Post updated after publishing. Remove Duplicates on the link ignores it. If you want re-promotion, dedupe on {{ $json.link + $json.isoDate }} instead.
• Article too long. Trim the text in an Edit Fields node, such as {{ $json.body.slice(0, 20000) }}, before sending it to the model.
• The HTML selector breaks after a redesign. The extract returns empty. Add an IF node that stops with Stop And Error when the body is shorter than 500 characters, so the error workflow alerts you.

#13Ledgerline walkthrough: the first two weeks

Ledgerline is a fictional accounts-payable software company. Details are illustrative.

Week one, the social manager reviewed every draft in the sheet and edited them in place. She kept a "changes" column describing each edit. Common notes: hooks too generic, too many questions, CTA repeated in every post.

Week two, marketing ops turned those notes into three prompt rules and added two of her edited posts as examples. Drafts needed fewer edits, and the sales snippet format was added at the SDR team's request.

#14Worked example: Ledgerline's webinar and blog repurposing

Ledgerline is a fictional accounts-payable software company. Details are illustrative.

Ledgerline published two posts a week and a monthly webinar. The social manager had time to promote each post once.

The repurposing workflow produced four formats per post into a sheet. After a month, the "used?" column showed LinkedIn drafts used most and X drafts rarely, so they dropped X and added a "sales email snippet" format the SDR team had asked for. Webinar transcripts were added as a second trigger, with the same structured output.

Walkthrough

1. RSS Feed Trigger on your blog feed.
2. Remove Duplicates: Remove Items Processed in Previous Executions, Value Is New, dedupe on the link field.
3. HTTP Request to fetch the article. HTML node to extract the main content (or use the feed's content field if complete).
4. Basic LLM Chain with a Structured Output Parser returning linkedin, x_post, newsletter, faq (array).
5. Google Sheets Append Row to a "Social drafts" sheet with the article URL and each format.
6. Slack message to the social channel: "Drafts ready for [title]" with the sheet link.
7. Social manager edits and schedules from the sheet.

#15Try it yourself

Run your last three blog posts through the workflow (use a manual trigger with pinned feed items). Compare the drafts with what your social manager would write. Note what had to change, and turn those notes into prompt rules.

#16Quick quiz

1. Which node stops the same post being repurposed twice?

Answer: Remove Duplicates, comparing against previous executions on the URL.

2. Why generate all formats in one call?

Answer: It is cheaper than one call per format, and the structured output is easy to split.

3. Should the workflow post directly to social?

Answer: Our view is no: write drafts and let a person schedule.

#17What should you check before the next lesson?

• New posts are picked up once only.
• Drafts land in a sheet or queue for people.
• Prompt rules include examples your team liked.

Next: AI visibility monitoring with n8n. Or return to the n8n for Marketers track.

#18Common questions

Can n8n post to LinkedIn? There is a LinkedIn node. We recommend drafts and human scheduling for brand safety.

Does the RSS trigger poll? Yes, it checks the feed on an interval. Check the node docs for options.

Can I repurpose webinars? Yes, from a transcript. Transcribe first, then use the same pattern.