Content & Social Media · n8n

YouTube-to-Blog Converter: every new video becomes a full SEO article, automatically

An n8n workflow that watches a YouTube channel's RSS feed, pulls the transcript of each new video with an Apify actor, and has Claude turn it into a structured blog post — title, headings, FAQ section — saved to Google Sheets ready to paste into your CMS.

difficulty Intermediatesetup 45 minresult One publish-ready article per video, minutes after upload
  1. 1

    Watch the channel feed

    Add an RSS Feed Trigger pointed at https://www.youtube.com/feeds/videos.xml?channel_id=YOUR_CHANNEL_ID — every YouTube channel has this free feed, no API key needed. It fires within minutes of a new upload.

  2. 2

    Get the transcript

    An HTTP Request node runs an Apify YouTube-transcript actor synchronously with the video URL. You get back the full spoken text with timestamps. Videos without captions fall back to auto-generated ones, which Claude cleans up fine.

  3. 3

    Write the article with Claude

    An HTTP Request to Claude with a detailed prompt: SEO title under 60 chars, meta description, H2/H3 structure, the speaker's key points preserved in written style (not transcribed speech), a 3-question FAQ, and the video embedded mid-article. Ask for markdown — it pastes cleanly everywhere.

  4. 4

    Queue for your review

    A Google Sheets node appends: date, video title, video URL, article markdown, and a status column defaulting to draft. Your Monday routine: open the sheet, read, tweak, publish. The writing is done; you're just editing.

Frequently asked questions

Whose videos can I convert?

Your own channel — that's the intended use: you already speak the content, this repurposes it into search traffic. Converting other people's videos into articles is plagiarism territory and can violate YouTube's terms; don't build your site on it.

Does Google penalize AI-written articles?

Google's guidance targets unhelpful content, not AI authorship. An article generated from your own spoken expertise, edited before publishing, is exactly the 'people-first' content they describe. The workflow saves drafts to a sheet rather than auto-publishing for precisely this reason — you review, then publish.

Can it post straight to WordPress?

Yes — add n8n's WordPress node after the sheet step (create post, status: draft). We ship it commented out in the workflow notes because auto-publishing unreviewed AI text is how sites get burned. Turn it on once you trust the output.

About this recipe. Recipes on FlowRecipesHub are written for business owners, not developers, and are tested before publishing — how recipes get made. Some ingredient links are affiliate links that cost you nothing — full disclosure.