A practical automation loop
Collect or generate the data that belongs in the video, map it to a Rendofy payload, submit the webhook request, and resume only when the callback reports a completed render. The MP4 URL becomes an ordinary data field for the next approved workflow step.
1. Trigger
Start from an RSS item, a record change, a form, or your own service event.
2. Render
POST JSON plus a callback URL to Rendofy and retain the returned job ID.
3. Deliver
Use the callback's video_url to download, store, or pass along the MP4.
Plan for an asynchronous result
A finished video is not returned inline with the initial request. Design your workflow so state survives between the request and callback. In n8n, a Wait node can resume the same execution; in a custom service, save the job context before accepting the callback.
Plan for capacity too
Flat monthly plans are determined by concurrent renders. That makes the capacity control visible: if every slot is in use, retry after one clears. It is safer than relying on an undocumented queue and makes the workload your workflow sends easier to reason about.