ScreenshotOne icon

ScreenshotOne

Render PDFs, screenshots, scrolling screenshots, and short videos using ScreenshotOne

Actions5

Overview

This node integrates with the ScreenshotOne service to render visual content from web sources. It supports generating screenshots, full-page screenshots, PDFs, scrolling screenshots, and short videos from URLs, raw HTML, or Markdown input. This is useful for automating the capture of website snapshots, creating PDF reports from web pages, or producing short video previews of web content.

Common scenarios include:

  • Automatically capturing website screenshots for monitoring or documentation.
  • Generating PDFs of web pages for offline reading or archiving.
  • Creating short video clips demonstrating website interactions or animations.
  • Producing scrolling screenshots that capture long pages in one image.

Properties

Name Meaning
Source The type of input to render. Options: URL, HTML, Markdown
URL The URL of the webpage to render (required if Source is URL)
HTML Raw HTML content to render (required if Source is HTML)
Markdown Markdown content to render (required if Source is Markdown)
Cache Enable or disable caching for this request
Cache TTL (Seconds) Time to live for cache in seconds (minimum 14400, maximum 2592000). 0 means default TTL
Cache Key Custom cache key string for this request

Note: The above properties are the general inputs related to the "Default" resource and operation you specified.

Output

The node outputs an array of items where each item contains a json field holding the response data from the ScreenshotOne API. The exact structure depends on the operation but generally includes:

  • For screenshots and full-page screenshots: image data or a URL to the rendered image in the requested format (PNG, JPG, WEBP).
  • For PDFs: a PDF file or link to the generated PDF.
  • For short videos and scrolling screenshots: video data or a URL to the video in MP4 or GIF format.

Binary data (images, PDFs, videos) is typically returned as base64 encoded strings within the JSON or accessible via URLs depending on the API response.

Dependencies

  • Requires an API key credential for ScreenshotOne service authentication.
  • The node calls ScreenshotOne API endpoints (take for images/PDFs and animate for videos).
  • No additional environment variables are required beyond the API key credential.

Troubleshooting

  • Invalid or missing API key: The node requires a valid API key credential. Ensure the API key is correctly configured in n8n credentials.
  • Invalid URL or unsupported source content: If the URL is unreachable or the HTML/Markdown content is malformed, the API may return errors or empty results.
  • Caching issues: If caching is enabled but results do not update, verify cache keys and TTL settings.
  • Unsupported format or operation: Selecting incompatible formats or operations may cause errors; ensure options match the selected operation.
  • Timeouts or slow responses: Rendering complex pages or long videos may take time; consider increasing timeout settings if available.

Links and References

Discussion