Overview
This node integrates with the ScreenshotOne service to render various types of visual content from web sources. It supports generating PDFs, screenshots (including full page and scrolling), and short videos from URLs, raw HTML, or Markdown input. This is useful for automating the creation of visual assets such as website snapshots, PDF reports, or video previews without manual intervention.
Practical examples include:
- Automatically generating a PDF report from a webpage URL.
- Capturing a full-page screenshot of a marketing site for archival.
- Creating a short video preview of a product page.
- Rendering Markdown content into a PDF or image for documentation purposes.
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 HTML content to render (required if Source is HTML) |
| Markdown | The Markdown content to render (required if Source is Markdown) |
| Landscape | Whether to render the PDF in landscape orientation (boolean) |
| Print Background | Whether to print background graphics in the PDF (boolean) |
| Cache | Enable or disable caching for this request (boolean) |
| Cache TTL (Seconds) | Time to live for cache in seconds; minimum 14400 (4 hours), maximum 2592000 (30 days) |
| Cache Key | Custom cache key string for this request |
Note: Although the node supports multiple operations, here only the "PDF" operation properties are relevant per your selection.
Output
The node outputs an array with one item per input. Each item contains a json field holding the response data from the ScreenshotOne API. For the PDF operation, this typically includes the generated PDF file data encoded appropriately (usually base64 or a direct binary buffer depending on n8n's handling).
If the node supports binary output (not explicitly shown here), it would represent the actual PDF file content suitable for saving or further processing.
Dependencies
- Requires an API key credential for the ScreenshotOne service.
- The node calls ScreenshotOne's API endpoints to generate the requested content.
- No additional environment variables are indicated beyond the API key credential.
Troubleshooting
- Invalid or missing API key: The node requires a valid ScreenshotOne API key. Ensure credentials are correctly configured.
- Invalid input data: Providing empty or malformed URL, HTML, or Markdown may cause errors or empty results.
- Cache misconfiguration: If caching is enabled but TTL or keys are invalid, unexpected behavior might occur.
- Unsupported formats or options: Using unsupported combinations of options (e.g., landscape with non-PDF format) could lead to errors.
- Network issues: Since the node depends on external API calls, network connectivity problems can cause failures.
Common error messages will likely relate to authentication failures, invalid parameters, or timeouts. Verify inputs and credentials first.
Links and References
- ScreenshotOne Official Website
- ScreenshotOne API Documentation (for detailed API usage and options)