Start hereintermediate40 min
Auto-Post Your Blog to Social With n8n + Claude
An n8n workflow watches an RSS feed, your blog or a source you curate, and for each new item it asks Claude to write a short, on-brand caption with a couple of hashtags, then sends it to your scheduler to be queued. Publishing and sharing stop being two separate chores, and your feed stays active without you opening a single social app.
Auto-Post Your Blog to Social With n8n + Claude
An n8n workflow watches an RSS feed, your blog or a source you curate, and for each new item it asks Claude to write a short, on-brand caption with a couple of hashtags, then sends it to your scheduler to be queued. Publishing and sharing stop being two separate chores, and your feed stays active without you opening a single social app.
Publishing should trigger sharing
Right now you do two jobs: write the post, then separately remember to promote it. The second one is the job that slips. This automation welds them together, the moment something new appears in your **RSS feed**, the sharing happens on its own. RSS is the quiet superpower here: nearly every blog and CMS publishes one automatically, and it is a tidy, machine-readable list of everything you post. That feed becomes the trigger for your entire social presence.
The three moves
Strip away the tools and this is just three steps in a row: - **Watch** — spot a new item in the RSS feed. - **Caption** — Claude writes a short, on-brand post about it. - **Queue** — the caption lands in your scheduler for a quick review. That is the whole shape. Build it once and it repeats forever, every new article you write gets a fresh social post without you lifting a finger.
Watch the feed
In n8n, start a workflow with an **RSS Read** node and paste your feed URL (try `yoursite.com/feed`). On the first run, set it to pull just one item so testing stays tidy. Hit Execute and the latest article appears as structured data, a **title**, a **link**, and a **summary**. That data is now flowing down the workflow, ready for Claude. n8n also remembers which items it has already seen, so nothing gets shared twice.
Let Claude write the caption
Add a [Claude](/tool/claude/) node and pass it the title and summary, not just the headline. The summary is what makes the caption specific instead of vague. Give it a tight brief: ``` Write a social caption for this post in a friendly, no-hype voice. Max 220 characters. End with one short question to invite replies. Add 1-2 relevant hashtags. Do not restate the title verbatim. Title: {{ $json.title }} Summary: {{ $json.summary }} ``` Claude returns a caption shaped for engagement and grounded in what the post actually says, not a generic "Check out our new blog post!" line.
Queue it, don't blast it
Add a final node that sends the caption to your social scheduler, or straight to a platform's posting API. Map Claude's caption to the post text and append the article link. The important choice here is to send it as a **queued draft**, not an instant publish. That gives you a safety net: posts sit waiting for a glance before they go live. Run the workflow once and confirm the queued post looks right before you trust it further.
Keep it honest and unique
Two settings keep this clean. First, leave posts as **drafts** until a week of captions has looked good, then let the queue auto-publish. Second, rely on n8n remembering processed items so each article is shared exactly once. If you ever reset the workflow, set "max items" low first, otherwise it will happily re-queue your entire archive in one burst.
Build the first two nodes today
You do not need the whole pipeline to feel the magic. In n8n, drop in just the **RSS Read** node pointed at your blog, then a **Claude** node with the prompt above, and execute. Watching Claude turn your latest post into a ready-to-go caption in one click is the moment this clicks, adding the queue step afterward takes ten more minutes.
Try this now
Your turn: open n8n and set up the first step. Just do step one now — the rest takes minutes. Save this guide to pick up where you left off.
FAQ
Should I really auto-post to social without reviewing?
The safe pattern is to queue, not publish instantly. Send posts to a scheduling queue so they sit as drafts you can glance over before they go live. Once you trust the captions, you can let the queue publish on its own.
Will the AI captions sound generic?
They are only as good as your prompt. Give Claude your voice, a length limit, and a rule like "no hype, one question to drive replies" and the output reads like you. Feeding it the article summary, not just the title, makes captions far more specific.
Where do the finished posts go?
Wherever you point the last node, your social scheduler of choice, or directly to a platform's posting API. The RSS watch and Claude caption steps stay identical; only the final destination changes.
What if my RSS feed does not exist or is messy?
Most blogs and CMS platforms expose an RSS feed automatically (often at /feed or /rss). If yours does not, a feed-generator tool can build one from a page. Point n8n at that and the rest works the same.