n8n Template Turns RSS Blog Posts Into 32-Second AI Shorts With Claude and Shotstack

n8n has published a publicly accessible workflow template for turning RSS blog posts into 32-second AI video Shorts. The workflow coordinates Claude Opus 5.5 and Shotstack: it takes blog content from an RSS feed, has Claude prepare a Shotstack edit, then renders a vertical 9:16 video. For teams already publishing written content, the template provides a concrete low-code blueprint for repurposing that work into short-form video.

The n8n workflow template for 32-second AI video Shorts documents the flow as an end-to-end example rather than a vague concept. Its stated purpose is to create Shorts from RSS blog posts with Claude and Shotstack, aligning the writing, asset planning, and rendering stages in one workflow.

That matters because a blog-to-video process often involves several distinct jobs: selecting source material, defining a script and visual sequence, producing a vertical edit, and preparing captions. The template shows how those handoffs can be represented in an automated workflow. It does not change the need for a content strategy, but it gives teams a documented starting point for connecting existing publishing output to a repeatable video format.

How the blog-to-Shorts workflow is structured

The workflow uses RSS or blog content as its input. Claude Opus 5.5 then writes the Shotstack edit specification, while Shotstack renders the resulting video. According to the template description, the edit can include voiceover, subtitles, animated text timed to music, and other planned assets.

The template description is unusually specific about the intended edit structure. It refers to 5 Nano Banana, two images, ElevenLabs music at 120 BPM, voiceover, subtitles, and animated text synchronized to the beat. Those details illustrate that the workflow is designed to generate a planned, timed short-form edit rather than simply place blog text over a static background.

What the template automates, and what it does not decide

The key automation is orchestration. n8n is the workflow layer that connects the content input, Claude's edit-writing task, and Shotstack's rendering capability. Claude's role is not merely to summarize a post. In this template, it creates the instructions that shape the eventual Shotstack video edit.

The documented output is also deliberately narrow: a 32-second vertical Short. That focus is useful for a practical implementation because it establishes a defined format, duration, and visual orientation. It should not be read as a guarantee that every blog post will suit the format equally well, or that one workflow design will match every brand's editorial style.

Teams evaluating the template should separate the verified workflow mechanics from the decisions that remain theirs. The published example provides a path from blog content to a rendered Short. It does not replace choices about which posts deserve video treatment, what brand voice the output should use, or how a finished video fits into a wider distribution plan.

For businesses with a steady publishing rhythm, that distinction is important. The workflow can reduce repetitive coordination between content, AI, and rendering tools, while editors or marketers retain control over source selection and publishing standards. A smaller team can start with a defined workflow instead of designing every connection from scratch.

Why the low-code approach is practical

The value of a public n8n template is not that it eliminates every implementation decision. Its value is that it exposes a working architecture that can be inspected and adapted. The pipeline makes the relationship between the three tools clear:

• n8n coordinates the workflow steps.
• Claude Opus 5.5 prepares the video edit instructions from blog content.
• Shotstack renders the instructions into a 9:16 Short.

This separation can help teams assess the process in manageable parts. A company can review whether its RSS feed is a suitable content input, whether the generated edit structure fits its preferred video style, and whether the rendered format matches the channels it intends to use. The template is a starting blueprint for that evaluation, not evidence that content review or adaptation is unnecessary.

Turning a template into a dependable publishing process requires more than connecting a few nodes. Scalevise can set up and productionize n8n workflows that connect content sources, AI services, and video tools while reducing repetitive handoffs. That helps your team turn existing blog output into a repeatable distribution workflow rather than a one-off demo. If you want a workflow tailored to your content and systems, discuss an n8n automation project with Scalevise.

Frequently Asked Questions

What does the n8n Claude and Shotstack template do?

It uses RSS blog content as input, has Claude Opus 5.5 write a Shotstack edit, and renders a 32-second AI video Short in 9:16 format with Shotstack.

What role does Claude play in the workflow?

Claude Opus 5.5 writes the Shotstack edit specification. The template description says that edit can include voiceover, subtitles, animated text, music, and planned assets.

What does Shotstack do in this n8n workflow?

Shotstack renders the video from the edit prepared in the workflow. The documented output is a 32-second vertical Short in 9:16 format.

Who is this blog-to-Shorts workflow most relevant for?

It is relevant for teams that publish blog content through RSS and want a documented low-code blueprint for converting selected posts into vertical short-form video.

Conclusion

n8n's published template demonstrates a real, publicly accessible workflow for moving from RSS blog content to a 32-second vertical Short using Claude and Shotstack. Its strongest practical value is the clear division of work between content input, AI-generated edit instructions, and video rendering. For teams exploring content automation, it is a useful blueprint for testing a more repeatable blog-to-video process.