The callback pattern
Create an HTTP Request node that posts to Rendofy, then 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.