Rendex
Integrations

Drop Rendex into the workflow you already use

n8n, Make, Zapier, Pipedream, and Activepieces for no-code automations. MCP for AI agents. Official SDKs for TypeScript and Python. And a plain REST API for everything else — your first rendered image in minutes, code optional.

Works withn8nZapierMakePower AutomatePipedreamActivepiecesMCP
PlusClaudeAI AgentCursorAI IDEWindsurfAI IDENode.jsRuntimeDenoRuntimeBunRuntimePythonLanguageGoLanguageJavaLanguagePHPLanguageRubyLanguageC# / .NETLanguage

n8n

Community node

Official n8n node with HTML, URL, and Markdown render modes. Authenticate once, then drop the Rendex step into any workflow — no Function node or raw HTTP required.

  • Native node — install from the n8n community registry
  • HTML → image, URL → screenshot, Markdown → PDF modes
  • Credential test hits /v1/credential-check (no wasted render)
  • Binary output pipes straight into Drive, Slack, or email nodes
// n8n workflow step
Trigger   →  Webhook / Schedule
Rendex    →  Render: HTML to Image
              html   = {{ $json.invoiceHtml }}
              format = png
Next step →  Google Drive — Upload
              file = {{ $binary.data }}

Make (HTTP module)

Template

There is no native Make app — and you do not need one. Use Make's built-in HTTP module to call Rendex, then pipe the rendered image or PDF into Drive, Slack, Notion, or any of Make's 2,000+ apps.

  • Works with the generic HTTP > Make a request module
  • POST JSON, get binary image/PDF or a JSON URL back
  • Drop the result into Drive, Slack, Notion, or email
  • No code — wire any trigger straight to a rendered image
# Make scenario — HTTP module
URL     = https://api.rendex.dev/v1/screenshot
Method  = POST
Headers = Authorization: Bearer YOUR_API_KEY
          Content-Type: application/json
Body    = {
  "html": "{{1.htmlBody}}",
  "format": "png"
}
# → pipe the binary response into Google Drive

Power Automate (HTTP action)

Template

No custom connector needed — call Rendex from Power Automate's built-in HTTP action, then save the rendered image or PDF to OneDrive, SharePoint, or an email. It's the #2 way Rendex is used.

  • Works with the built-in HTTP action (premium connector)
  • POST JSON to /v1/screenshot/json, get a base64 image/PDF back
  • Decode with base64ToBinary() into a Create file action
  • Save to OneDrive, SharePoint, or attach in Outlook
# Power Automate — HTTP action
URI     = https://api.rendex.dev/v1/screenshot/json
Method  = POST
Headers = Authorization: Bearer YOUR_API_KEY
          Content-Type: application/json
Body    = { "html": "{{triggerBody()?['html']}}",
            "format": "pdf" }
# → Create file: base64ToBinary(body('HTTP')?['data']?['image'])

Zapier

Native action

Native Zapier action with rendering presets — social card, thumbnail, full-page capture, PDF report, OG image. Automate across 7,000+ apps with no code.

  • Native Rendex actions in the Zapier editor — no code
  • Capture screenshots, render HTML, generate PDFs, extract text
  • Polling + webhook callbacks for async jobs
  • Built-in retries, logging, and error handling
# Example Zap: Weekly competitor screenshots
Trigger  →  Schedule by Zapier — Every Monday 9am
Action   →  Rendex — Capture Screenshot
             url      = https://competitor.com
             format   = png
             fullPage = true
Action   →  Slack — Send to #market-intel
             file = {{Rendex.file}}

Pipedream

Native action

Native Rendex action in Pipedream. Render HTML or a URL to an image or PDF, then pipe the base64 result into Slack, Gmail, Drive, S3, or any of Pipedream's 3,000+ connected apps. Drop into a code step for the full REST surface.

  • Native Render to Image action — Connect Account once
  • HTML → image and URL → screenshot, PNG/JPEG/WebP/PDF
  • Base64 output pipes straight into Slack, Gmail, Drive, or S3
  • Code step exposes the full REST API with the same key
# Pipedream workflow
Trigger  ->  HTTP / Schedule / App event
Rendex   ->  Render to Image
              html   = {{steps.trigger.event.body.html}}
              format = png
Slack    ->  Send Message
              file = {{steps.rendex.$return_value.image}}

Activepieces

Native piece

Native open-source Rendex piece. Render HTML, a URL, or Markdown to an image or PDF, then pipe the rendered file into any Activepieces piece. Every piece is also exposed as an MCP tool, so the same action is callable by your AI agents — on Activepieces Cloud or self-hosted.

  • Native Render to Image piece — connect your key once
  • HTML, URL, or Markdown → PNG/JPEG/WebP/PDF
  • File output pipes straight into Drive, Slack, or Gmail
  • Auto-exposed as an MCP tool for Claude, Cursor, Windsurf
# Activepieces flow
Trigger  ->  Webhook / Schedule / App event
Rendex   ->  Render to Image
              source = Markdown
              format = pdf
Drive    ->  Upload File
              file = {{ step_2.file }}

MCP Server

AI-native

Native Model Context Protocol server so Claude, Cursor, Windsurf, and any MCP-aware agent can render images and PDFs as a single tool call.

  • Remote endpoint at mcp.rendex.dev
  • Local stdio via npx @copperline/rendex-mcp
  • Semantic tool definitions (not raw REST)
  • Per-key rate limiting & edge auth
// Claude Desktop config
{
  "mcpServers": {
    "rendex": {
      "url": "https://mcp.rendex.dev/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

TypeScript / JavaScript SDK

npm

Official SDK with full type safety, zero external dependencies, and support for every API feature. Install and render in three lines.

  • Full TypeScript types for all params & responses
  • Zero external dependencies
  • Sync & async render modes
  • Batch, webhooks, geo-targeting support
npm install @copperline/rendex

import Rendex from "@copperline/rendex"

const rendex = new Rendex("your-api-key")
const { image } = await rendex.renderHtml(
  "<h1>Hello</h1>",
  { format: "png" },
)

Python SDK

PyPI

Official Python SDK with type hints and minimal dependencies. Render HTML, capture screenshots, and generate PDFs in three lines.

  • Full type hints for IDE autocompletion
  • Minimal dependencies (httpx only)
  • Sync & async client support
  • All API features supported
pip install rendex

from rendex import Rendex

client = Rendex("your-api-key")
result = client.render_html(
    "<h1>Hello</h1>",
    format="png",
)
# result.image → bytes

REST API

HTTP

A plain REST API that works with any language or HTTP client. JSON request body, binary or JSON response. No SDK required — this is what every integration above calls under the hood.

  • POST /v1/screenshot — render any URL or HTML
  • POST /v1/screenshot/batch — up to 500 URLs
  • JSON request body, binary or JSON response
  • Works with cURL, fetch, axios, requests, or any client
curl -X POST https://api.rendex.dev/v1/screenshot \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://example.com",
    "format": "png",
    "fullPage": true
  }' \
  --output screenshot.png

cURL / CLI

Shell

No installation needed. Test the API from your terminal with a single cURL command — great for scripting and CI/CD pipelines.

  • Zero install — works anywhere cURL runs
  • Shell scripting and CI/CD integration
  • Pipe output to files or other tools
  • Perfect for quick testing and prototyping
# Capture a screenshot in one command
curl -X POST https://api.rendex.dev/v1/screenshot \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url":"https://stripe.com","format":"png"}' \
  -o stripe.png
Workflow Recipes

Copy-paste workflow blueprints

Step-by-step recipes that wire a trigger to a Rendex render — Stripe invoices in n8n, Airtable OG images, batch URL captures with webhooks. Each ships a real config and a rendered preview.

Browse Recipes

Ready to integrate?

Get your API key in seconds. 100 free renders/month. No credit card required.