Rendex Is Now a Verified n8n Community Node

The Rendex n8n node passed the n8n team's verification review and went live on n8n Cloud on April 30. Search "Rendex" on the n8n canvas and the node appears. No JSON file editing, no manual npm installs inside a self-hosted instance.

This post covers what the verified Rendex n8n node provides, how to set it up in under five minutes, and how to use it as an AI Agent tool for autonomous web capture.

Why Verification Matters

Before the verified status, adding Rendex to an n8n workflow meant using the generic HTTP module: configure the endpoint URL manually, build the request body by hand, set the Authorization header, and parse a binary response yourself. Every update to the API meant updating the HTTP node config.

The verified Rendex n8n node replaces all of that with a purpose-built node: typed dropdowns for resources and operations, a dedicated credential type for your API key, and typed fields for every capture parameter. n8n's credential store handles the key; you never paste it into a request body.

Verified status also means n8n reviews the node on each release before it reaches users. Self-hosted instances with verified community nodes enabled pull updates through the standard n8n update path.

Install the Node

On n8n Cloud, the node is available by default. Open any workflow, click the "+" button to add a node, and search "Rendex".

On a self-hosted instance, go to Admin Panel > Community Nodes and enable verified community nodes if the toggle is off. Then search the canvas as above. The package name is n8n-nodes-rendex if you need it for allowlists.

Add Credentials

After adding the node to a workflow, click Credentials > Create New > Rendex API. Paste your API key (get one at rendex.dev/login). The key starts with rdx_live_. Save the credential and the node is ready.

Capture a Screenshot

Set Resource to Screenshot and Operation to Capture. Enter a URL, choose a format in Additional Options, and execute the workflow. The node outputs binary data (the image) alongside a JSON metadata item.

{
  "resource": "screenshot",
  "operation": "capture",
  "url": "https://example.com",
  "additionalOptions": {
    "format": "png",
    "fullPage": true,
    "viewportWidth": 1440,
    "blockAds": true
  }
}

For PDF output, set format to pdf in Additional Options. Page size, margins, and print backgrounds are all configurable. See the n8n integration docs for the full parameter list.

Submit a Batch

The Batch > Submit operation takes a newline-separated list of URLs and submits them as a single batch request. Rendex processes them in parallel and returns a batch ID. Poll the batch status with Batch > Get Status or set a webhook URL in Additional Options to receive a callback when the batch finishes.

{
  "resource": "batch",
  "operation": "submit",
  "urls": "https://northwindanalytics.com/\nhttps://northwindanalytics.com/pricing\nhttps://northwindanalytics.com/docs\nhttps://northwindanalytics.com/blog\nhttps://northwindanalytics.com/annual-report",
  "defaults": {
    "format": "png",
    "fullPage": true
  }
}

Batch limits depend on your plan. Each captured URL returns a signed storage URL you can pass to a downstream node to upload, email, or store. Try the free screenshot tool to test individual captures before wiring up a batch.

Output: a Batch Capture Report

The workflow below submits five URLs, waits for the batch to complete, and passes the results to a Code node that renders a report via the Rendex n8n node's Screenshot > Capture operation with an HTML template.

Use as an AI Agent Tool

The Rendex n8n node is built with usableAsTool: true, which means you can attach it directly to an n8n AI Agent node. The agent receives the node as a callable tool and decides when to invoke it based on the conversation or task context.

{
  "type": "n8n-nodes-base.agent",
  "parameters": {
    "agent": "toolsAgent",
    "tools": ["rendex"]
  }
}

In practice this means an AI Agent can capture a screenshot mid-task without any extra branching logic. The agent calls the Rendex n8n node the same way it calls a search tool or a calculator. Pair it with a vision model node downstream to analyze what was captured.

What the Node Covers

The Rendex n8n node exposes four resources:

• Screenshot: Capture (sync) and Capture Async. Sync returns binary data in the same workflow step. Async fires the job and returns a job ID immediately, which is useful for long-running full-page captures.
• Document: Extract. Turns any URL into clean Markdown, JSON, or article HTML pulled from the fully-rendered page. Useful for feeding scraped content to an LLM node downstream.
• Job: Get Status. Polls an async capture job for progress and the signed result URL.
• Batch: Submit and Get Status. Submit up to 500 URLs per request and track the batch through to completion.

Limits and Notes

A few things to keep in mind:

• Async polling: Capture Async returns a job ID, not the image. Add a Job > Get Status node in a loop or configure a webhook URL in Additional Options so Rendex calls your n8n webhook trigger on completion.
• Batch inputs are URL-only: The Batch Submit operation does not accept HTML or Markdown payloads in the URLs list. To render an HTML template to multiple outputs, loop over Screenshot > Capture with Source set to HTML.
• Batch size caps: The maximum URLs per batch depends on your plan. Check the pricing page for plan-level limits.
• Binary output: Sync captures return binary data in n8n's binary item format. Connect to a Write Binary File node or an email attachment node downstream.

Next Steps

The n8n integration docs list every parameter available in Additional Options, including wait strategies, viewport sizing, cookie injection, and geo-targeting.

For a complete workflow that generates invoice PDFs from an HTML template triggered by a webhook, read Automate Invoice and Document Generation in n8n with Rendex.

Get an API key at rendex.dev/login. The free tier includes 500 captures per month to get started.