Full Page Screenshot
AI-generatedOverview
This node performs a full page screenshot rendering using the ScreenshotOne service. It supports rendering from different input sources such as URL, HTML, or Markdown. The node allows customization of the output format (PNG, JPG, WEBP), response type (JSON URL, binary base64, or empty), and full page scroll delay. It also supports caching options to optimize repeated requests. This node is useful for capturing entire web pages as images for documentation, testing, or archival purposes.
Use Case Examples
- Capture a full page screenshot of a website by providing its URL and receive a JSON response with the screenshot URL.
- Render a full page screenshot from custom HTML content and get the image as a base64-encoded binary string.
- Use caching to speed up repeated full page screenshot requests with a custom cache key and TTL.
Properties
| Name | Meaning |
|---|---|
| Source | The type of input to render, which can be a URL, HTML, or Markdown content. |
| URL | The URL to render as a screenshot. Required if Source is URL. |
| HTML | The HTML content to render as a screenshot. Required if Source is HTML. |
| Markdown | The Markdown content to render as a screenshot. Required if Source is Markdown. |
| Response Type | Determines the format of the rendering result, either JSON with a URL, binary base64 string, or empty response. |
| Format | The image format of the screenshot output, applicable for full page screenshots. |
| Full Page Scroll Delay (Milliseconds) | The delay in milliseconds to wait during full page scrolling before capturing the screenshot. |
| Cache | Enable or disable caching for the screenshot request to optimize repeated calls. |
| Cache TTL (Seconds) | Time to live for the cache in seconds, controlling how long the cached screenshot is valid. |
| Cache Key | Custom cache key to uniquely identify the cached screenshot request. |
Output
JSON
json- The JSON response containing the screenshot result, typically including the URL or metadata of the rendered full page screenshot.
Dependencies
- ScreenshotOne API service
- An API key credential for authentication
Troubleshooting
- Ensure the input source matches the selected source type (URL, HTML, or Markdown) to avoid unsupported source errors.
- Verify that the ScreenshotOne API credentials are correctly configured to prevent authentication errors.
- If caching is enabled, check cache key and TTL values to ensure proper cache behavior.
- Common errors include unsupported source or operation errors, which can be resolved by selecting valid options.
Links
- ScreenshotOne Documentation - Official documentation for the ScreenshotOne API and usage guidelines.