How to Render HTML to Images in Make.com (No-Code)

Make.com is great at moving data between apps. It is less obvious how to turn that data into a finished image. If you want to render an HTML invoice, an OG card, or a certificate to a PNG inside a Make scenario, there is no drag-and-drop module that does it. You build it with one HTTP request.

This guide renders raw HTML to an image in Make using the generic HTTP module and the Rendex rendering API. To be clear up front: Rendex does not yet ship a native Make app. You connect through Make's built-in HTTP module, which works on every Make plan and gives you the full Rendex REST surface with nothing to install. Full setup is in the Make integration docs.

Prerequisites

• A Make.com account on any plan
• A Rendex API key. The free plan covers 100 renders/month. Get one at rendex.dev/login.
• A trigger or earlier module that produces the data you want to render

Why the HTTP Module

Make connects to most services through prebuilt apps, but it also ships a generic HTTP module for any REST API. Since Rendex has no dedicated Make app, the HTTP module is the supported path, and it has an upside: you control the request body directly, so every Rendex parameter is available with no app version to wait on.

Step 1: Create a Rendex API Key

Sign up at rendex.dev/login, open your dashboard, and click Create API Key. A Rendex key is rdx_ followed by 22 characters, a single segment with no environment prefix like live_ or test_. Copy it somewhere safe; you'll paste it into the HTTP module's header next.

Step 2: Add and Configure the HTTP Module

In your scenario, add the HTTP → Make a request module after your trigger. Fill the fields as below.

• Method: POST
• URL: https://api.rendex.dev/v1/screenshot
• Headers: add one header, Authorization with value Bearer rdx_… (your key). Make sends Content-Type: application/json automatically when you use the JSON body type.
• Body type: Raw / JSON (application/json)

Step 3: Send the HTML

Put your markup in the html field of the JSON body. There is no hosted page in the loop: Rendex renders the raw HTML you send and returns the image. Set format, width, and height to control the output.

{
  "html": "<div style=\"font-family: system-ui; padding: 48px\"><h1 style=\"color: #e2571a\">Invoice #1042</h1><p>Billed to: Acme Co.</p></div>",
  "format": "png",
  "width": 1200,
  "height": 630
}

Escape inner double quotes so the JSON stays valid, or assemble the body in a prior Make module and pass it through. To screenshot a live page instead of rendering markup, swap html for "url": "https://example.com". For a document, set "format": "pdf". The full parameter list (full-page scroll, dark mode, wait strategy, PDF page options) is in the API reference and works as-is inside the JSON body.

Here is the same call as raw cURL, useful for testing the request before you wire it into Make:

curl -X POST https://api.rendex.dev/v1/screenshot \
  -H "Authorization: Bearer rdx_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "html": "<div><h1>Invoice #1042</h1></div>",
    "format": "png",
    "width": 1200,
    "height": 630
  }' --output invoice.png
# Get your API key at https://rendex.dev/login

Step 4: Use the Image Downstream

By default Rendex responds with the binary image itself. Make exposes it as the HTTP module's Data output, which you map into any binary-capable module:

• Google Drive / Dropbox — Upload a file: map Data to the file content, set a filename like invoice.png.
• Email — Send an email: add an attachment and map Data as the content.
• Another HTTP module: forward Data to a downstream API.

Need a base64 string or a JSON response instead of raw bytes? Call /v1/screenshot/jsonwith the same headers and body, set Make's Parse response to Yes, and map the base64 data.image field.

Two Quick Scenarios

The pattern is the same everywhere: trigger, HTTP module to Rendex, then a module that consumes the image.

• Invoice on each new order: Google Sheets trigger → HTTP POST to /v1/screenshot with your invoice HTML and "format": "pdf" → Email or Drive upload of the returned Data.
• OG card per record:Airtable trigger → HTTP POST with a branded HTML card at 1200×630 → upload the PNG and use its URL as the record's og:image.

Troubleshooting

• 401 Unauthorized: The header value must be exactly Bearer followed by your rdx_ key. A common slip is dropping the Bearer prefix or leaving a trailing space.
• Invalid JSON body: Inner quotes in your HTML must be escaped. Set the body type to JSON and let Make validate it, or build the JSON in a prior module.
• Downstream module shows no image: If you called /v1/screenshot, map the binary Data output, not a text field. If you called /v1/screenshot/json, enable Parse response and map data.image.

Next Steps

Try the render before building the scenario. The free HTML-to-image tool shows exactly what your markup produces, with no key required. If you use n8n as well as Make, the native node version of this workflow is in the n8n invoice automation guide.

When you're ready to wire it up, grab a free API key (100 renders/month, no credit card) and follow the full field-by-field setup in the Make integration docs.