CORTEXFLOW · FREE FOREVER

Automation

Social Media Auto-Poster & Content Repurposer

↓ Download workflow JSON

Import in n8n: Workflows → ⋯ → Import from file, then add your credentials. Free download with a free account.

How it works

  1. RSS Feed Read — watches your blog’s RSS feed for new posts.
  2. IF New Post Found — passes the workflow on only when the feed item has a valid link.
  3. Repurpose with AI — GPT turns the post title and summary into three drafts: an X post (under 280 characters), a LinkedIn long-form post, and a short hook line.
  4. Format Drafts — packages the AI output into a clean drafts field and keeps the source link.
  5. Slack — Review Drafts — sends all three drafts to your #content-review channel for review.
  6. Wait for Approval — pauses the execution until you approve or reject it in the n8n execution view. Nothing publishes while it waits.
  7. IF Approved — continues only if you clicked Approve; rejected runs end here.
  8. Publish Posts — sends the drafts to your social scheduler via a placeholder API (https://api.your-social-scheduler.com/v1/publish). Swap it for Buffer, Typefully, or the X API.
  9. Slack — Published — sends you a confirmation once the posts are live.

Set up steps

You’ll need:

  • n8n (self-hosted or cloud)
  • Your blog’s RSS feed URL (e.g. https://your-blog.com/rss.xml)
  • An OpenAI account — get an API key at platform.openai.com → API keys
  • A Slack workspace — create a channel like #content-review and connect Slack in n8n when prompted
  • A social scheduler account (Buffer, Typefully, or the X API) — only needed when you want live publishing
  1. Download the workflow JSON using the download button on this page.
  2. In n8n, go to Workflows → ⋯ → Import from file and select the JSON.
  3. Set your feed URL — open RSS Feed Read and replace https://your-blog.com/rss.xml with your blog’s real RSS feed URL.
  4. Create your OpenAI credential — in n8n go to Credentials → New → OpenAI, paste your API key, save. Open Repurpose with AI and select your credential.
  5. Create your Slack credential — in n8n go to Credentials → New → Slack OAuth2 API, complete the OAuth flow, save. Open both Slack nodes, select your credential, and confirm the channel.
  6. Point the publisher at your scheduler — open Publish Posts and replace the placeholder URL and header-auth credential with your real scheduler (Buffer, Typefully, or the X API endpoint). Until you do this, the workflow stops safely at approval with nothing published.
  7. Activate the workflow (toggle, top-right), then publish a blog post to test it.

Customize it

  • More platforms — edit the prompt in Repurpose with AI to add Threads, Facebook, or a newsletter blurb.
  • Change the tone — add style instructions (e.g. “casual, no hashtags”) to the same prompt.
  • Different review channel — change the channel in both Slack nodes.
  • Auto-publish a platform — remove the approval gate only if you’re comfortable; the workflow is designed so nothing publishes without your approval.

Workflow nodes

This workflow is built from 9 nodes. Here's what each one does:

#NodeTypeWhat it does
1 RSS Feed Read RSS Feed Read Fetches new items from an RSS feed.
2 IF New Post Found IF Splits the flow into branches based on a condition.
3 Repurpose with AI OpenAI Sends a prompt to OpenAI and returns the AI's answer.
4 Format Drafts Set Holds editable configuration values — fill in your own settings here before activating.
5 Slack — Review Drafts Slack Posts messages or reads data in Slack.
6 Wait for Approval Wait Pauses the workflow until a condition or time is met.
7 IF Approved IF Splits the flow into branches based on a condition.
8 Publish Posts HTTP Request Calls an external API or webhook endpoint.
9 Slack — Published Slack Posts messages or reads data in Slack.

Setup instructions

1. Add your credentials

In n8n go to Credentials → New, create each credential below, then open the named node and select it:

NodeCredential to add
Repurpose with AI OpenAI API
Slack — Review Drafts Slack OAuth2
Publish Posts HTTP Header Auth
Slack — Published Slack OAuth2

Use cases

Every blog post you publish should become social posts, but repurposing is the task that never happens: it sits below client work until the post is stale and the moment is gone. This template closes the loop automatically, without handing a robot the publish button. RSS Feed Read watches your blog's feed, and when IF New Post Found sees a valid new link, Repurpose with AI turns the title and summary into three drafts: an X post under 280 characters, a LinkedIn long-form post, and a short hook line. Format Drafts packages them neatly, and Slack Review Drafts drops all three into the content-review channel. Then the workflow pauses at Wait for Approval. Nothing publishes while it waits; rejected runs simply end. Approved runs continue through IF Approved to Publish Posts, a placeholder scheduler endpoint you point at Buffer, Typefully, or the X API, and Slack Published confirms once the posts are live. It is built for bloggers, solo founders, and small teams who want consistent distribution with a human still in charge.

The solo blogger publishing twice a week

A blogger writing two in-depth posts a week knows each one deserves an X post and a LinkedIn version, and also knows that writing them is exactly what gets skipped on a busy Friday. The drafts arrive in Slack within minutes of publishing, already in the post's voice, and approval takes thirty seconds from the phone. The hook line doubles as the snippet for scheduling tools or the newsletter subject line. Because nothing publishes without approval, a post the blogger is unsure about can sit in review until the angle is right.

  • Variation: add a style instruction to the Repurpose with AI prompt, such as casual with no hashtags, so every draft arrives already matching the blogger's voice.

The SaaS startup repurposing the changelog

A three-person SaaS startup ships a changelog post every two weeks, and each one contains three or four features users would love if they ever heard about them. The workflow watches the changelog RSS: the X post announces the headline feature in under 280 characters, the LinkedIn version tells the longer story of why it was built, and the hook line becomes the in-app announcement banner.

  • Variation: edit the Repurpose with AI prompt to add a fourth draft for Threads or Facebook, so one approval covers every channel the startup cares about.

The freelance social media manager with five clients

A freelancer managing social for five small businesses used to keep five tone-of-voice documents and a lot of anxiety. Now each client gets its own copy of the workflow pointed at their blog's RSS feed, with the client's voice baked into the Repurpose with AI prompt and drafts routed to a per-client Slack channel. The freelancer's job shifts from writing first drafts to editing and approving, which roughly triples the client load one person can carry. The approval gate is the selling point: clients see that nothing goes live without a human check.

  • Variation: give each client their own review channel in both Slack nodes so drafts, approvals, and published confirmations stay cleanly separated per account.

The founder-led LinkedIn personal brand

A founder publishing one thoughtful essay a week wants LinkedIn to be the main stage, not an afterthought. The LinkedIn long-form draft arrives minutes after the post goes live, structured for the platform rather than pasted from the blog, while the X post and hook line handle discovery elsewhere. The founder reads the draft in Slack, tweaks the opening line to taste, and approves. The whole distribution job takes five minutes and happens the same morning the essay publishes, when the ideas are still fresh.

  • Variation: keep the approval gate even as volume grows; the workflow is deliberately designed so removing it is a conscious choice, not an accident.

The newsletter writer squeezing more from each issue

A newsletter writer with 8,000 subscribers publishes weekly, and each issue contains at least two ideas strong enough to travel on social. The workflow watches the newsletter archive RSS, and every issue becomes an X post plus a hook line the writer reuses as next week's subject-line inspiration. The LinkedIn draft gives the essay a second life with the professional audience. Because the source is the RSS summary rather than the full text, the drafts tease rather than reproduce, which is exactly what drives clicks back to the issue.

  • Variation: point a second copy of the workflow at the podcast or video RSS feed if the newsletter repurposes into other formats, so every medium feeds the same review channel.

← All templates