Actions49
- Airbnb Actions
- AppStore Actions
- Booking Actions
- Company Insight Actions
- Emails & Contact Actions
- Expedia Actions
- G2 Review Actions
- Geocoding Actions
- GetApp Review Actions
- Google Map Actions
- Google Search Actions
- Indeed Actions
- Phone Identity Finder Actions
- Phones Owner Actions
- Product Hunt Actions
- Target Review Actions
- TikTok Profile Actions
- TripAdvisor Actions
- Trustpilot Actions
- Twitter Profile Actions
- Universal AI Scraper Actions
- Walmart Review Actions
- WebPage Screenshoter Actions
- Whitepages Addresses Scraper Actions
- Yellow Pages Search Actions
- Yelp Actions
- YouTube Actions
- Zillow Actions
Overview
The WebPage Screenshoter node allows users to capture screenshots or PDF snapshots of web pages by providing URLs. It supports capturing either the visible viewport or the full page, with customizable viewport dimensions and output formats. This node is useful for monitoring website appearance, archiving web content, generating previews, or automating visual testing.
Typical use cases include:
- Generating thumbnail images of product pages or articles.
- Archiving web pages as PDFs for compliance or record-keeping.
- Capturing screenshots for UI/UX review or bug reporting.
- Automating visual content generation for marketing or social media.
Properties
| Name | Meaning |
|---|---|
| Query | URL(s) of the web page(s) to capture (e.g., https://www.apple.com/iphone/) |
| Region | Country setting to influence screenshot capture (may affect localized content rendering) |
| Type | Output format of the screenshot: WebP, PNG, JPEG image, or PDF document |
| Full Page | Whether to capture the entire scrollable page (true) or just the visible viewport (false) |
| Width | Width in pixels of the browser viewport used for capturing the screenshot |
| Height | Height in pixels of the browser viewport |
| Async Request | If enabled, the request is processed asynchronously; a webhook callback can be used to get results later |
| Webhook | URL to which Outscraper will send a POST request once the asynchronous screenshot task finishes |
| Additional Fields | Collection of optional parameters: |
| - Fields | Comma-separated list of specific fields to return |
| - UI | Whether to execute the request as a UI task |
Output
The node outputs JSON data containing the screenshot result. The exact structure depends on the API response but typically includes:
- Metadata about the screenshot task (status, timestamps).
- The screenshot content encoded in base64 or a URL link to the image/PDF file.
- Additional requested fields if specified.
If the output is an image or PDF, it can be used downstream in workflows for storage, further processing, or sending via email.
Binary data handling is not explicitly detailed here, but since screenshots are returned as files, the node likely provides the image/PDF as binary data or a downloadable link.
Dependencies
- Requires an active connection to the Outscraper API service.
- Needs an API key credential configured in n8n for authentication.
- Internet access to reach target web pages and the Outscraper API endpoint.
- Optional webhook URL must be publicly accessible if asynchronous requests are used.
Troubleshooting
- Invalid URL or unreachable web page: Ensure the
Queryproperty contains valid, reachable URLs. Network issues or incorrect URLs will cause failures. - API authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
- Unsupported output type: Confirm that the
Typeproperty is one of the supported formats (webp, png, jpeg, pdf). - Asynchronous request issues: If using async mode, ensure the webhook URL is correct and publicly accessible to receive callbacks.
- Viewport size problems: Extremely small or large viewport dimensions may cause unexpected results; use reasonable width and height values.
- Rate limits or quota exceeded: Outscraper API may limit usage; check your account status if requests fail repeatedly.