Site-Shot community node: public URL → PNG/JPEG binary

I’m Alexey from Site-Shot. We released n8n-nodes-siteshot 0.1.1: a small community node for turning a public HTTP(S) URL into a PNG or JPEG binary file.

The basic path is Manual Trigger → Site-Shot → a node that accepts a binary file:

  • Set the URL and a Site-Shot API credential.
  • Optionally choose Full Page and viewport dimensions.
  • Read the image from the data binary field (or the field name you select). Rename the file downstream when saving multiple captures.

The node checks the API’s error field before returning binary data, rather than passing an error placeholder on as a screenshot. It does not schedule, store images or retry captures by itself.

Scope and cost: self-hosted n8n with community nodes enabled; documented testing covers n8n 2.40.5 only. We are not presenting this as an n8n-verified node or claiming n8n Cloud support. Read the README’s compatibility and dependency-advisory notes before installing.

The node code is MIT-licensed, but the Site-Shot API is paid, with no free API credits. Plans start at $5/month; accepted capture attempts may consume quota even if rendering fails.

Source and setup · npm package · API pricing

If you already need public-page screenshots in an n8n workflow, what happens to the image next: storage, an email report, or image analysis?

Disclosure: maintainer post, prepared with AI assistance.

Your node’s binary output looks like a useful starting point for a screenshot report. Disclosure: I build PixelVault (https://pixelvault.dev). A possible next step is an n8n HTTP Request that uploads the screenshot and returns a CDN URL for the report. Would you be interested in comparing a small Site-Shot → PixelVault example? I’d keep the capture and hosting steps separate so users can choose either independently.