Scrolling Screenshot
AI-generatedOverview
This node performs a scrolling screenshot operation using ScreenshotOne. It captures a scrolling screenshot of a webpage or rendered content from a URL, HTML, or Markdown input. The node supports options to specify the video format (MP4 or GIF), duration of the video, and whether to wait for the scroll to complete before capturing. It is useful for capturing long or dynamic web pages that require scrolling to capture the full content.
Use Case Examples
- Capturing a scrolling screenshot of a webpage by providing its URL.
- Rendering HTML content and capturing a scrolling screenshot video in MP4 format.
- Using Markdown content as input and generating a GIF scrolling screenshot.
Properties
| Name | Meaning |
|---|---|
| Source | The type of input to render, which can be URL, HTML, or 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). |
| Response Type | Determines the format of the rendering result output. JSON returns a URL, Binary returns a base64-encoded string, and Empty returns no content. |
| Format | The video format of the scrolling screenshot output, either MP4 or GIF. |
| Scroll Complete | Whether to wait for the scroll to complete before capturing the screenshot. |
| Duration | Duration of the scrolling screenshot video in seconds. |
| Cache | Enable or disable caching for the request. |
| Cache TTL (Seconds) | Time to live for cache in seconds. |
| Cache Key | Custom cache key for the request. |
Output
JSON
url- URL of the rendering result when response type is JSON.data- Base64-encoded binary data of the rendering result when response type is Binary.
Dependencies
- ScreenshotOne API
- An API key credential for ScreenshotOne
Troubleshooting
- Ensure the source input matches the selected source type (URL, HTML, or Markdown).
- Verify that the API key credential for ScreenshotOne is correctly configured and has necessary permissions.
- If using caching, ensure cache key and TTL are set appropriately to avoid stale or missing data.
- Common errors include unsupported source or operation values, which will throw descriptive errors indicating the issue.
Links
- ScreenshotOne Documentation - Official documentation for ScreenshotOne API and usage.