Rendex
Use Case

Render Images & PDFs Inside Your n8n Workflows

Drop the official Rendex node into any n8n workflow to turn HTML into images, screenshot live URLs, render Markdown to a PDF, or mint a hosted og:image link. The output flows straight into Gmail, S3, Slack, or any downstream node — no Function-node glue. The same node can even schedule a page-change Watch that fires back into n8n when a page moves.

The Problem

n8n builders constantly need to attach a rendered image or PDF to a workflow — a branded social card, an invoice, a Markdown release note, a dashboard snapshot — but n8n has no native rendering. The workarounds are ugly: stand up a self-hosted Puppeteer container and call it over HTTP, wrestle a Code node and base64, or chain three external services. Each one adds infrastructure you now have to keep alive.

The Solution

The official Rendex community node renders HTML, a URL, or Markdown to PNG, JPEG, WebP, or PDF on Cloudflare's edge and returns it as native n8n binary data. Paste your API key once, pick a mode, and the rendered file is ready for the next node — email attachment, object-storage upload, Slack post, or HTTP webhook. The same node also mints hosted Render Link URLs (a signed og:image link, nothing to store or move) and can create page-change Watches that POST a signed webhook back into n8n on a real change. No container to host, no cold starts, no base64 plumbing. (For the full node reference and setup, see the n8n integration page and /docs/n8n.)

See it in action

An n8n workflow: a new Google Sheets order row triggers the Rendex node to render an HTML invoice to PDF, which an email node sends as an attachment.

Get Started in Minutes

rendex-node.json
{
  "node": "Rendex",
  "parameters": {
    "resource": "screenshot",
    "operation": "capture",
    "source": "html",
    "html": "<div style='width:1200px;height:630px;display:flex;align-items:center;justify-content:center;background:#0f172a;color:#fff;font-family:system-ui;font-size:48px'>{{ $json.title }}</div>",
    "format": "png",
    "width": 1200,
    "height": 630
  }
}
what-the-node-sends.sh
# What the Rendex node sends under the hood
curl -X POST https://api.rendex.dev/v1/screenshot \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"html":"<div>...</div>","format":"png","width":1200,"height":630}' \
  --output card.png

100 free API calls/month — no credit card required. Get your API key and start building.

Built for This Use Case

Verified Community Node

Rendex is a Verified Community Node on n8n Cloud — find it in the nodes panel and add it with one click, no manual install. Authenticate once with your API key. Also installs on self-hosted n8n from Settings → Community Nodes.

HTML, URL, Markdown & Render Links

Pick the mode per node — HTML to image, URL screenshot, Markdown to PDF, or a hosted Render Link (a signed og:image URL). Binary output drops straight into the next step; the Render Link is a URL you paste into a CMS or Slack.

Template With Workflow Data

Inject upstream JSON into your HTML template with n8n expressions — dynamic invoices, certificates, and OG images, one per item.

Batch & Loop Friendly

Pair with Loop Over Items / Split In Batches to render hundreds of social cards or invoices in a single workflow run.

Edge Rendering, No Container

Renders on Cloudflare's edge in seconds. No self-hosted Puppeteer, no n8n memory blowups on large or image-heavy pages.

Reliable on Slow Pages

Best-attempt mode and wait-for-selector mean a slow SPA returns a usable capture instead of hanging your workflow.

Start Free, Scale as You Grow

100 calls/month free. Starter at $69/mo for 10K calls (or $58/mo billed annually — 2 months free). Pro at $179/mo for 100K calls.

Frequently Asked Questions

Related Resources