Use a Pipedream trigger to launch a browser, wait for the page state you need, capture the page or an element, and send the resulting image to the next workflow step. A scheduled trigger is suitable for recurring snapshots; an app event or webhook is better when a particular event should produce the screenshot. The practical browser pattern is Puppeteer running in a Pipedream code step, with a temporary file or encoded image passed to storage, email, or another service.
Choose the capture architecture first
Pipedream workflows are event-triggered sequences of steps. The trigger can be a timer, an incoming webhook, or an event from a connected app. After the trigger, choose one of three capture approaches:
- Puppeteer in a code step: maximum control over navigation, viewport, waits, selectors, cookies, and browser actions.
- A managed screenshot action: less browser code, but you must confirm that the action and its current fields are still available in your Pipedream account.
- A hosted browser such as Browserless: useful when you want a remote browser while retaining Puppeteer-style controls. The Pipedream community example demonstrates viewport configuration, element selection, and exporting the result; its 2022 publication should not be treated as evidence of current limits or pricing.
The examples below use Puppeteer because it makes the workflow behavior explicit.
Build a scheduled screenshot workflow with Puppeteer
1. Add a trigger
- Create a new Pipedream workflow.
- Select a Schedule trigger for hourly, daily, or another recurring cadence. For event-driven captures, select the app event or webhook that should start the workflow.
- Give the workflow a stable name and note the expected timezone. A schedule determines when navigation starts; it does not determine when the page is ready.
2. Add a browser code step
Add a Node.js code step and use Pipedream’s browser support. This example navigates to a page, waits for a page-specific selector, and writes a full-page PNG to /tmp:
#1 Best Overall
- CRISP CLARITY: This 23.8″ Philips V line monitor delivers crisp Full HD 1920x1080 visuals. Enjoy movies, shows and videos with remarkable detail
- INCREDIBLE CONTRAST: The VA panel produces brighter whites and deeper blacks. You get true-to-life images and more gradients with 16.7 million colors
- THE PERFECT VIEW: The 178/178 degree extra wide viewing angle prevents the shifting of colors when viewed from an offset angle, so you always get consistent colors
- WORK SEAMLESSLY: This sleek monitor is virtually bezel-free on three sides, so the screen looks even bigger for the viewer. This minimalistic design also allows for seamless multi-monitor setups that enhance your workflow and boost productivity
- A BETTER READING EXPERIENCE: For busy office workers, EasyRead mode provides a more paper-like experience for when viewing lengthy documents
import puppeteer from "@pipedream/browsers";
export default defineComponent({
async run({ steps, $ }) {
const browser = await puppeteer.launch();
try {
const page = await browser.newPage();
await page.setViewport({ width: 1440, height: 900, deviceScaleFactor: 1 });
await page.goto("https://example.com", {
waitUntil: "domcontentloaded",
timeout: 60000
});
// Replace this with a selector that proves the page is ready.
await page.waitForSelector("main", { timeout: 30000 });
const path = "/tmp/site-shot.png";
await page.screenshot({ path, fullPage: true, type: "png" });
return {
path,
url: page.url(),
title: await page.title()
};
} finally {
await browser.close();
}
}
});The selector and URL are examples. A main element may exist before charts, images, or client-rendered data finish loading, so select a condition that represents the content you actually need.
3. Use a delay only when it is intentional
A Pipedream community example waits ten seconds before calling page.screenshot. Treat that as a demonstration, not a universal readiness rule. A fixed delay can be useful for a page with predictable animation, but it wastes time on fast pages and can still be too short on slow ones.
await new Promise(resolve => setTimeout(resolve, 10000));Prefer waitForSelector, a navigation condition, or an application-specific readiness marker. For network-heavy pages, combine a reasonable navigation timeout with a selector wait rather than waiting indefinitely for every request to finish.
Control what gets captured
Full page versus viewport
Use fullPage: true when you need the complete document. Omit it, or set it to false, when the deliverable should match the visible viewport.
await page.screenshot({ path: "/tmp/viewport.png", fullPage: false });Set the viewport before navigation so responsive layout is rendered consistently:
Rank #2
- CRISP CLARITY: This 22 inch class (21.5″ viewable) Philips V line monitor delivers crisp Full HD 1920x1080 visuals. Enjoy movies, shows and videos with remarkable detail
- 100HZ FAST REFRESH RATE: 100Hz brings your favorite movies and video games to life. Stream, binge, and play effortlessly
- SMOOTH ACTION WITH ADAPTIVE-SYNC: Adaptive-Sync technology ensures fluid action sequences and rapid response time. Every frame will be rendered smoothly with crystal clarity and without stutter
- INCREDIBLE CONTRAST: The VA panel produces brighter whites and deeper blacks. You get true-to-life images and more gradients with 16.7 million colors
- THE PERFECT VIEW: The 178/178 degree extra wide viewing angle prevents the shifting of colors when viewed from an offset angle, so you always get consistent colors
await page.setViewport({ width: 1280, height: 800, deviceScaleFactor: 2 });A larger device scale factor produces a denser image and a larger file. Keep the viewport and scale fixed for visual comparisons.
Capture one element
For a chart, invoice, hero section, or dashboard card, locate the element and pass its bounding box to the screenshot call:
const element = await page.$(".report-card");
if (!element) throw new Error(".report-card was not found");
await element.screenshot({ path: "/tmp/report-card.png", type: "png" });Element capture is generally more stable than cropping a full-page image later, because the browser computes the element’s current dimensions.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Hide or alter page content
You can inject CSS before capture to hide cookie prompts, fixed headers, or other elements that obscure the content:
await page.addStyleTag({
content: ".cookie-banner, .chat-widget { display: none !important; }"
});Only hide elements when you are authorized to alter the presentation. If the banner is part of what you are documenting, leave it visible.
Pass the image to the next Pipedream step
The browser step’s /tmp file is temporary. Use it during the same workflow run, then upload or send it to its destination. A common community pattern is to export screenshot bytes as base64 and decode them in a later code step. The exact format depends on the downstream action, so inspect that step’s input contract.
Rank #3
- Clear visuals. Fluid motion: A 144Hz refresh rate and 1ms MPRT deliver smooth, tear‑free motion across work, gaming, and streaming for clearer, more fluid viewing.
- Eye comfort: TÜV Rheinland 3‑star* certification reduces harmful blue light while preserving stunning color quality without compromise. *TÜV Rheinland 3-star eye comfort certification.
- Wide viewing angle: Get consistent views across a wide 178° /178° viewing angle.
- In-Plane Switching (IPS): See excellent color accuracy and consistency across wide viewing angles with In-plane Switching (IPS) technology.
- Ultra-thin bezels: Maximize your viewing experience with thin bezels.
Return base64 from the browser step
import fs from "node:fs";
import puppeteer from "@pipedream/browsers";
export default defineComponent({
async run({ $ }) {
const browser = await puppeteer.launch();
try {
const page = await browser.newPage();
await page.goto("https://example.com", { waitUntil: "domcontentloaded", timeout: 60000 });
await page.waitForSelector("main", { timeout: 30000 });
const buffer = await page.screenshot({ fullPage: true, type: "png" });
return {
filename: "site-shot.png",
mimeType: "image/png",
base64: Buffer.from(buffer).toString("base64")
};
} finally {
await browser.close();
}
}
});Decode in a later step
import fs from "node:fs";
export default defineComponent({
async run({ steps, $ }) {
const shot = steps.browser_step.$return_value;
const path = `/tmp/${shot.filename}`;
fs.writeFileSync(path, Buffer.from(shot.base64, "base64"));
return { path, bytes: fs.statSync(path).size };
}
});Replace browser_step with the actual step name. Then connect an S3, Google Drive, email, HTTP, or other destination step and map the file or bytes according to that integration’s documented input.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteUse Pipedream’s managed GetScreenshot action
Pipedream’s GetScreenshot integration listing documents a URL input, PNG, JPEG, and PDF output choices, optional email delivery, a DOM element selector, extra parameters, and API-key authentication. The listing is old enough that you should verify the action, field names, and authentication screen in your account before building a production workflow.
Keep the API key in Pipedream’s connected-account or authentication configuration, not as a literal string in source code. Use the selector field when the action supports element capture, and verify whether the returned value is a file, URL, or encoded data before mapping it to the next step.
Hosted-browser option: Browserless
A Pipedream community workflow shows Browserless used with Puppeteer: the workflow sets viewport dimensions, navigates, selects an element, takes a screenshot, and exports the result. This is a useful model when you want browser execution outside the Pipedream runtime. Because the example dates from 2022, confirm current Browserless connection syntax, authentication, limits, and output behavior before relying on it.
Or skip the browser setup
ScreenshotNeo provides a website screenshot API and MCP server. One GET request returns PNG, JPEG, WebP, or PDF. Before capture it accepts cookie or consent banners and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each cleanup step can be disabled. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and the response identifies the result with X-Page-Verdict and X-Billed headers.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11It also supports full-page capture with lazy images loaded, CSS-selector element capture, dark mode, 12 device presets and custom viewports, retina scale, PDF paper sizes and page ranges, custom CSS and JavaScript, clicks before capture, selector hiding, waits for selectors, delays or network idle, blocking ads, trackers, requests or resource types, custom headers, cookies, user agents and Authorization, timezone and geolocation, transparent backgrounds, resizing, TTL-based caching, signed image links, asynchronous jobs with signed webhooks, bulk capture of up to 100 URLs per call, a usage API, and an OpenAPI specification. Common screenshot-API parameter names also work, which can simplify migration.
Rank #4
- CURVED FOR ENHANCED ENGAGEMENT: An immersive viewing experience with a curved monitor that wraps more closely around your field of vision; It creates a wider view, enhancing depth perception and minimizing peripheral distraction
- SMOOTH PERFORMANCE FOR SEAMLESS CONTENT: Stay in the action when playing games, watching videos, or working on creative projects; The 100Hz refresh rate reduces lag and motion blur so you don't miss a thing in fast-paced moments¹
- MORE GAMING POWER: Gain the edge with optimizable game settings; Color and image contrast can be adjusted to see scenes more vividly and spot enemies hiding in the dark; Game Mode adjusts any game to fill the screen so you can view every detail²
- KEEP IT EASY ON THE EYES: Care for your eyes and stay comfortable, even during long sessions; Advanced eye comfort technology certified by TÜV reduces eye strain by minimizing blue light and reducing irritating screen flicker²
- INCREASED VERSATILITY: Connect to more; Plug devices straight into your monitor for increased flexibility, making your computing environment even more convenient
Use the API from Pipedream’s HTTP step or a code step. The following calls are complete examples; replace the URL and key.
cURL
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpPython
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)Node.js
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);See the ScreenshotNeo documentation for request options and response handling. An MCP server supplies take_screenshot, get_page_info, and capture_pdf tools to Claude, Cursor, and other MCP clients.
The Free plan includes 1,000 shots per month without a card. Paid plans start at $5 for 3,000 shots; every feature is available on every plan. Create a free ScreenshotNeo account to try the Pipedream HTTP pattern.
Reliability, performance, and cost decisions
Make readiness deterministic
- Wait for a selector containing the data you need, not merely for the first HTML response.
- Use a bounded timeout and fail the run clearly when the condition never appears.
- Keep viewport, device scale, timezone, and authentication consistent when comparing screenshots.
Reduce runtime and image size
- Capture an element instead of a full document when only a component is required.
- Use JPEG or WebP when a smaller photographic image is acceptable; use PNG for sharp text or transparency.
- Block unnecessary requests only after confirming that they do not supply page content.
- Close the browser in a
finallyblock so failures do not leave a running session.
Understand temporary storage
A /tmp path is appropriate for handoff during one run, not as durable archival storage. Upload the result before the workflow ends, and retain metadata such as the source URL, capture time, viewport, and page verdict.
Troubleshooting
The workflow times out during navigation
Increase the navigation timeout only when the site is legitimately slow. Check DNS, authentication, redirects, and blocked resources. Use waitUntil: "domcontentloaded" and then wait for the required selector instead of waiting for every network request.
Best Value
- 【INTEGRATED SPEAKERS】Whether you're at work or in the midst of an intense gaming session, our built-in speakers provide rich and seamless audio, all while keeping your desk clutter-free.
- 【EASY ON THE EYES】 Protect your eyes and enhance your comfort with Blue-Light Shift technology. This feature reduces harmful blue light emissions from your screen, helping to alleviate eye strain during long hours of use and promoting healthier viewing habits.
- 【WIDEN YOUR PERSPECTIVE】Our sleek minimal bezel design ensures undivided attention. The nearly bezel-free display seamlessly connects in a dual monitor arrangement, delivering an unobstructed view that lets you focus on more at once, completely distraction-free.
The screenshot is blank or incomplete
Confirm that JavaScript finished rendering and that the selector exists. Increase the selector timeout, scroll to trigger lazy loading, or wait for a page-specific “loaded” marker. A ten-second delay is only an example and may be either excessive or insufficient.
The selector is not found
Inspect the current DOM and account for iframes, shadow DOM, responsive breakpoints, and class names generated at runtime. If the content is inside an iframe, obtain the frame and query inside it rather than querying the top-level page.
The file cannot be used by the next step
Check whether the destination expects a path, binary data, base64, or a public URL. Decode base64 explicitly and write it to /tmp when a file is required. Upload it before the run ends because temporary files are not an archive.
The managed action is missing or has different fields
Verify the GetScreenshot action in the current Pipedream workspace. Its documented listing is older, so names, availability, and output shape may have changed.
The page shows a login, CAPTCHA, or consent wall
Provide authorized cookies or headers where the service permits it. Do not attempt to bypass access controls. For consent overlays, remove them only when that reflects your permitted capture objective; ScreenshotNeo can handle known consent, newsletter, and chat overlays before capture.
FAQ
Can a Pipedream workflow take a screenshot after an app event instead of on a schedule?
Yes. Use the app event or webhook as the trigger, then run the same browser or API capture step.
Recommended Free Tools
Should I save screenshots as PNG, JPEG, or PDF?
Choose PNG for lossless UI text and transparency, JPEG or WebP for smaller raster files, and PDF when the recipient needs a document with page dimensions or ranges.
Is a ten-second wait enough for every website?
No. It is a sample delay from a community example. Use a condition that represents the content your workflow must capture.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
