Integration

Rendex for Activepieces

Drop the native Rendex piece into any Activepieces flow to turn HTML, a URL, or Markdown into an image or PDF — the rendered result comes back as a ready-to-use file, so the next step can attach, upload, or email it. Start free with 100 renders a month, no card.

Activepieces is open-source, self-hostable automation with a library of connected pieces — but no built-in way to render a finished image or PDF. The Rendex piece fills that gap: connect your key once, pick HTML, a URL, or Markdown, and pipe the rendered file straight into Slack, Gmail, Drive, or S3. And because every Activepieces piece is also exposed as an MCP tool, the same Render to Image action is instantly available to Claude, Cursor, and Windsurf.

Get Free API Key Activepieces Setup Guide

Activepieces flow

  Trigger        →  Webhook / Schedule / App event
        │
        ▼
  Rendex (piece)
        action = Render to Image
        source = Markdown
        format = pdf
        │  returns { file, format, bytesSize }
        ▼
  Google Drive — Upload File
        file = {{ step_2.file }}

How It Fits Your Workflow

Trigger

Any Activepieces trigger — a webhook, a schedule, or an app event from the piece library.

Rendex piece

Render HTML, a URL, or Markdown to a PNG, JPEG, WebP, or PDF on the edge.

Downstream

Pipe the rendered file into Slack, Gmail, Drive, or S3 — or call it as an MCP tool.

What You Can Do

Native Render to Image piece

Search "Rendex" in the Activepieces piece library and connect your API key once. The Render to Image step is then available in every flow — no HTTP step to hand-configure. Ships as the npm package @activepieces/piece-rendex.

HTML, URL, or Markdown — four formats

A single Source dropdown switches between raw HTML (an invoice, OG card, or certificate), a live URL for a screenshot, or Markdown rendered to a styled page. Output as PNG, JPEG, WebP, or PDF, with an optional full-page capture — all on every plan, including Free.

File output, ready to attach

The piece returns the render as a proper Activepieces file — not a raw base64 string — so it drops straight into a Google Drive upload, a Slack message, or a Gmail attachment with no decode step in between.

Callable as an MCP tool

Activepieces exposes every piece as an MCP tool, so the Render to Image action is instantly available to Claude, Cursor, Windsurf, and any MCP-aware agent — the same connection, no extra setup.

Full REST surface via Custom API Call

The piece also ships a Custom API Call action. Point it at any Rendex endpoint — content extraction, batch captures, async jobs, or Mustache data templating — using the same Rendex connection you already authorized.

Open-source, self-hostable, zero infra

Rendering runs on Rendex's edge, so there is no Chromium or Puppeteer to install. And because Activepieces is open-source, the same Rendex piece works whether you run Activepieces Cloud or your own self-hosted instance.

Recipes for Activepieces

Turn Markdown into a Branded PDF in Activepieces

Activepieces

Render a Markdown document — a doc, changelog, or approved article — to a branded PDF inside an Activepieces flow with the native Render to Image piece. No CSS, no headless browser, and the same step is callable by your AI agents.

More rendering recipes

Built for other tools, but the same Rendex API powers them — adapt the trigger and the render step works the same.

Render HTML to a PNG in Make (Correct HTTP Module Setup)

Make

A pre-wired Make HTTP module that renders HTML to a PNG with Rendex on the first try. Copy the exact request body so you never hit the 400 'send exactly one of url, html, or markdown' error.

Left: a raw Stripe payment event JSON with customer, amount, and invoice number. Right: the same data rendered as a clean, branded PDF invoice with a PAID badge, itemized line items, and a total — ready to email.

Auto-Generate Invoice PDFs from Stripe in n8n

n8n

Render a branded PDF invoice the moment Stripe reports a payment, using one n8n workflow and Rendex — then email it or store a hosted link. No PDF library, no headless browser to host.

Left: an Airtable grid row with title, subtitle, and author columns. Right: the same row rendered as a 1200x630 branded OG card on an orange-to-dark gradient, with the hosted URL written back into the row's ogImageUrl field.

Auto-Generate OG Images from Airtable Rows (Make & Zapier)

MakeZapier

Turn every Airtable row into a branded Open Graph image. A Make HTTP module or Zapier action calls Rendex's hosted render link, then writes the og: URL straight back to the row.

Left: a JSON array of four URLs (stripe.com, vercel.com, linear.app, railway.app) submitted in a single batch POST. Right: a 2×2 grid of finished screenshot cards, each labeled with its host and a green '200 · signed' status from its HMAC-signed webhook callback.

Batch Screenshot a List of URLs with Webhook Delivery in n8n

n8n

Submit a whole list of URLs to Rendex in one batch request and receive each screenshot through an HMAC-signed webhook as it finishes — driven on a schedule from n8n.

Render an HTML Financial Report or Invoice to PNG in Python

Python SDK

Turn an HTML financial report, invoice, certificate, or data table into a crisp PNG from a server-side Python script — one render_html() call, no headless Chrome to host. Embed the image in a generated PDF or report deliverable.

Email an HTML Report as a PNG Attachment in n8n

n8nMake

Render an HTML report or KPI summary to a PNG with Rendex on a schedule, then email it as an attachment to your team — one n8n workflow, no headless browser to host. Works the same in Make.

Browse all recipes

Start Free, No Card Required

100 renders/month on the free plan. Upgrade only when you scale.