n8n video rendering

Make video rendering a normal step in your n8n workflow.

Rendofy works with n8n's standard HTTP Request and Wait nodes: submit JSON, pause the same execution for the callback, then use the returned MP4 URL downstream.

Verified n8n Community Node
Rendofy is available directly in n8n Cloud. Open n8n, choose Add a node, search for “Rendofy”, select the node, connect your Rendofy API key, then choose Resource: Render and Operation: Create.

The callback pattern

The verified Rendofy node is the preferred setup: add it after the node that prepares your JSON, select Resource: Render and Operation: Create, then provide a public callback URL. For a manual HTTP setup, create an HTTP Request node that posts to Rendofy and set callback_url to the active execution's Wait-node resume URL. The request returns a job ID. The Wait node resumes that same n8n execution when Rendofy posts the completed render.

callback_url: {{ $execution.resumeUrl }}

POST https://api.rendofy.com/webhook/render-intake
api_key: {{ $env.RENDOFY_API_KEY }}

Handle the resumed body correctly

On n8n 2.32.0, the Wait node resume data is exposed as a webhook envelope. The completed Rendofy payload is in $json.body, not directly at the root. Normalize that object before reading video_url, then give a download node the normalized URL.

This behavior was verified in a real RSS → Rendofy execution: the callback resumed the same execution, the MP4 downloaded successfully, and its output was inspected.

Keep the key out of workflow JSON

Use an n8n environment variable or credential. The rendered result is an MP4 delivered by callback; it is not an instruction to enable a publishing destination. Add any downstream publisher only when you have explicitly configured and authorized it.