Make.com integration

Let long renders finish outside your scenario.

Synchronous video rendering can outlast Make.com’s HTTP response window. Rendofy accepts a render job quickly, processes it asynchronously, and calls a Make custom webhook when the MP4 is ready.

Make documents a default 40-second HTTP wait when a module receives no response data. Custom Apps can configure longer timeouts, up to 300 seconds. Async callbacks avoid keeping that request open while a render runs. Make timeout documentation.

A callback keeps the scenario moving

Use an HTTP module to submit scene JSON. Rendofy acknowledges the queued job with HTTP 202, renders in the background, then posts the finished result to a Custom Webhook trigger. Your scenario resumes from that callback instead of holding an HTTP request open during rendering.

HTTP module

POST JSON, callback URL, and API key to Rendofy.

Background render

Capture the queued response and let the scenario end or continue its own work.

Custom Webhook

Receive completion data with the job ID and finished video URL.

Configure the Make HTTP module

Set the method to POST, send JSON, and map your Custom Webhook URL into callback_url. Keep the API key in a Make connection or protected variable rather than hard-coding it into a shared scenario.

Request body

{
  "api_key": "{{connection.api_key}}",
  "callback_url": "{{custom_webhook.url}}",
  "payload": {
    "quote": "A new release, ready to share",
    "author": "Example Studio"
  }
}

Endpoint: https://api.rendofy.com/webhook/render-intake. Set Content-Type to application/json. Use the payload fields supported by your Rendofy template.

Immediate acknowledgement

HTTP/1.1 202 Accepted
{
  "status": "queued",
  "job_id": "render-job-id"
}

Callback received by Custom Webhook

{
  "job_id": "render-job-id",
  "status": "completed",
  "video_url": "https://cdn.example.com/render.mp4"
}

Callback fields shown are an example. Map the actual callback response fields into the next Make modules.

Build the scenario around the result

After the Custom Webhook trigger receives the completed callback, map video_url into your storage, notification, or publishing modules. Add a separate route for failed jobs if your scenario needs to notify an operator or retry safely.

Run 3 Free RendersRead API docs