Workflow 04 / Marketing

Content Repurposing Engine

One new blog post becomes LinkedIn, X, newsletter and quote-card copy waiting for approval.

Trigger
New post in an RSS feed
Size
8 nodes, 3 credentials
Typical build
4 working days
Tools
n8n, RSS, OpenAI API, Google Sheets, Slack

Example scenario: B2B fintech, two long-form articles a week, two-person marketing team

The problem

The marketing team had no time to turn articles into social posts. Distribution was inconsistent and most articles were shared once, by the founder, on a Friday evening.

What the workflow does

The solution

n8n watches the blog RSS feed, fetches each new article and extracts the body. An LLM with a written brand-voice guide produces a LinkedIn post, a five-post X thread, a newsletter blurb and three quote cards. Everything lands in the content calendar sheet scheduled for 9:00 the next day with Status "Awaiting approval". Slack announces the row and the team approves by setting Status to Approved in the sheet. Invalid AI output is reported to Slack instead of being queued.

The flow

Drawn from the real JSON

Node names, order and branches are read from the exported file at build time, so this diagram can never drift from what n8n will show you. Dashed lines are connections; amber ones leave an IF, a Switch or an error output.

Download n8n JSON
TriggerAI stepApp actionTransformBranch
8 nodes

Scroll sideways to see all branches

error1. RSS: New Blog PostRSS01New Blog Post2. HTTP: Fetch ArticleHTTP02Fetch Article3. HTML: Extract BodyHTML03Extract Body4. LLM: RepurposeLLM04Repurpose5. Parse AssetsCode05Parse Assets6. Sheets: Content CalendarSheets06Content Calendar7. Slack: Parse FailureSlack07Parse Failure8. Slack: #content ApprovalSlack08#content Approval

Node by node

#NodeTypeWhat it does
01RSS: New Blog PostTriggerPolls blog.example-fintech.example/rss.xml every hour
02HTTP: Fetch ArticleApp actionGET article URL
03HTML: Extract BodyTransformExtracts the article title and body text
04LLM: RepurposeAI stepChat completion (gpt-4o-mini), JSON-only output
05Parse AssetsTransformValidates the LLM answer and builds the calendar row. Invalid output leaves through the error output.
06Sheets: Content CalendarApp actionAppends a row to the "Queue" tab
07Slack: Parse FailureApp actionPosts a message to #content
08Slack: #content ApprovalApp actionPosts a message to #content

How a run goes

  1. RSS trigger checks the blog feed every hour.

  2. HTTP Request fetches the article page; the HTML node extracts title and body.

  3. The LLM repurposes the text into four formats using the brand-voice rules.

  4. A Code node validates all four formats and schedules the publish slot; invalid output goes to a Slack warning instead.

  5. Google Sheets appends the row to the content calendar with status "Awaiting approval".

  6. Slack posts a preview to the content channel; the team approves by setting Status to Approved in the sheet.

Tools and credentials

Credentials are referenced by name inside the JSON. Create each one in n8n under Credentials, using these names, and the nodes connect automatically.

Credential nameWhat you need
OpenAI – FlowforgeAPI key from platform.openai.com
Slack – Flowforge BotBot token with the chat:write scope
Google Sheets – OpsGoogle OAuth client with the Sheets API enabled

Setup in about 30 minutes

  1. Import the file. In n8n open Workflows, then Import from file, and pick content-repurposing.json. The workflow arrives inactive.

  2. Create the 3 credentials listed above with exactly those names.

  3. Replace the placeholders with your own IDs:

    • REPLACE_WITH_CALENDAR_SHEET_ID in “Sheets: Content Calendar”
  4. Adapt it to your business.

    • Set the feed URL in the RSS trigger to your blog.
    • Paste your brand-voice guide (tone, banned phrases, three example posts) into the system prompt of "LLM: Repurpose".
    • Create the calendar sheet with a "Queue" tab and these columns: Publish on, Source, URL, LinkedIn, X thread, Newsletter, Quotes, Status.
    • Publishing stays manual by design: approval is the Status column in the sheet. To auto-post, add a Buffer or LinkedIn step that runs when Status changes to Approved.
  5. Connect error reporting. Import error-reporter.json once, then open this workflow’s Settings and choose it as the Error workflow. Failed runs are posted to Slack and logged, with a link to retry.

  6. Test, then activate. Run the first node with sample data, check each output in the execution view, then switch the workflow to active. Keep the test run for your records.

Example figures for the scenario above, not guarantees

What this kind of build changes

12assets per article, in about 90 seconds
3×LinkedIn impressions per article
9 hmarketing time saved weekly
100%of posts approved by a human

Use it, or have it built for you

The JSON is free to import and adapt. If you would rather have it wired to your own stack and tested on your data, a single flow like this is a fixed-price project.