Turn one RSS item into a downloadable video.

1. Configure the source safely

Import Rendofy's RSS-to-video workflow template into n8n and set its RSS source. Store the demo or account key in the n8n environment as RENDOFY_API_KEY; do not put a real key in the workflow JSON. The render request uses that environment variable and creates a unique callback URL from the active execution.

2. Submit the render, then pause the same execution

The workflow posts the normalized RSS data to https://api.rendofy.com/webhook/render-intake. Its callback_url is $execution.resumeUrl. Rendofy returns a queued job acknowledgement, then posts the completed result to that Wait-node resume URL.

{
  "api_key": "{{ $env.RENDOFY_API_KEY }}",
  "callback_url": "{{ $execution.resumeUrl }}",
  "payload": { "title": "...", "subtitle": "..." }
}

3. Normalize the callback body before reading video_url

This is the important n8n 2.32.0 detail: a Wait node resumes with a webhook envelope, so the Rendofy callback is available as $json.body. The template's Normalize Rendofy Callback node unwraps that body. Downstream nodes should use the normalized object and its video_url, not assume it lives at the root of the resumed item.

4. Download and inspect the rendered MP4

Configure the download node to fetch the normalized video_url as binary data. The tested output downloaded and inspected successfully: an H.264 MP4 at 1920×1080, 30 fps, approximately six seconds. That result validates this template path only; it does not guarantee a 9:16 aspect ratio for future payloads.

Optional publishing comes after validation

The template intentionally leaves YouTube credentials unconfigured. If you later add a publishing action, supply your own credential and make that a separate, explicitly authorized workflow decision. This tutorial does not configure or execute a publishing step.