Overview
This node integrates with the ScreenshotOne service to render visual content from various input sources. It supports generating screenshots, full-page screenshots, PDFs, scrolling screenshots, and short videos from URLs, raw HTML, or Markdown content. This is useful for automating the capture of website previews, generating PDF reports from web pages, creating video demos of page interactions, or archiving web content visually.
Practical examples include:
- Automatically capturing a screenshot of a webpage URL for monitoring or reporting.
- Rendering Markdown content as an image for social media sharing.
- Generating a PDF version of a webpage for offline reading or distribution.
- Creating a short video recording of a webpage scroll or animation for presentations.
Properties
| Name | Meaning |
|---|---|
| Source | The type of input to render. Options: URL, HTML, Markdown |
| URL | The URL to render (required if Source is URL) |
| HTML | The raw HTML content to render (required if Source is HTML) |
| Markdown | The Markdown content to render (required if Source is Markdown) |
| Format | Output format for screenshots and full page screenshots. Options: PNG, JPG, WEBP |
| Full Page Scroll Delay (Milliseconds) | Delay in milliseconds before capturing full page scroll screenshots (minimum 400 ms) |
| Full Page | Whether to capture the entire page in a screenshot (boolean) |
| Cache | Enable or disable caching for this request (boolean) |
| Cache TTL (Seconds) | Time to live for cache in seconds (minimum 14400, max 2592000) |
| Cache Key | Custom cache key string for this request |
Note: The above properties are specific to the "Screenshot" operation under the "Default" resource.
Output
The node outputs JSON data containing the response from the ScreenshotOne API. This typically includes metadata about the rendered content and a base64-encoded string representing the generated file (image, PDF, or video). The exact structure depends on the operation but generally provides the rendered file's data ready for further processing or saving.
If binary data is output (e.g., images, PDFs, or videos), it represents the visual rendering result of the requested operation.
Dependencies
- Requires an API key credential for authenticating with the ScreenshotOne service.
- Network access to the ScreenshotOne API endpoint.
- Proper configuration of the API key credential within n8n.
Troubleshooting
Common issues:
- Invalid or missing API key will cause authentication failures.
- Incorrect input source selection without providing corresponding data (e.g., selecting URL but leaving URL empty).
- Unsupported format or invalid parameter values may cause API errors.
- Cache misconfiguration might lead to stale or unexpected results.
Error messages:
- Authentication errors indicate problems with the provided API key; verify and update credentials.
- Validation errors suggest missing required parameters or invalid values; ensure all required fields are correctly filled.
- Timeout or network errors may occur if the ScreenshotOne service is unreachable; check network connectivity.
Links and References
- ScreenshotOne Official Website
- ScreenshotOne API Documentation (for detailed API parameters and usage)