Free tools Windows power users keep installed
One-click scans. No signup required.
To capture a website screenshot in an Activepieces automation, add the Browserless piece to a flow, connect it using Custom auth, then choose its Capture Screenshot action. Activepieces describes this as a no-code action. The current integration listing confirms the action has 13 fields, but does not enumerate them or explain the screenshot result’s data format, so configure those fields using the labels and help shown in your own builder rather than relying on guessed settings.
Use the Browserless action in an Activepieces flow
The documented route is the Browserless piece’s Capture Screenshot action. It is intended for a flow that captures a website as one step in an automation, rather than for taking screenshots of your own application while running tests. You can add later steps to route or process the result, but Activepieces’ integration listing does not establish the output’s exact shape or prescribe a storage destination.
- Create or open a flow. In the Activepieces flow builder, open the flow where you want the capture to happen. Choose the trigger that fits your automation. The Browserless listing does not specify a trigger requirement for screenshots; it reports zero triggers for the piece itself, so the flow’s starting event is a separate design choice.
- Add Browserless. Add the Browserless piece as a step. Activepieces describes the piece as a headless browser automation tool for scraping websites, taking screenshots, and more.
- Set up its connection. Select Custom auth, the authentication method identified on the integration page. The listing reviewed here does not state which exact credential value belongs in the connection form. Use the current form’s instructions and Browserless account documentation to identify it; do not assume a field name, token format, or URL.
- Select the action. Choose Capture Screenshot from the Browserless actions.
- Complete the fields displayed in your builder. The integration listing says the action has 13 fields but does not publish their names or detailed meanings in the reviewed content. Follow the current labels and any field-level help to provide the target website and capture settings. Do not assume options for dimensions, full-page capture, output format, authentication to the target site, or storage unless the action actually exposes them.
- Test and inspect the step output. Run the flow with a page you are allowed to access. Inspect the action’s output in the run details before adding a downstream step: the integration listing does not specify whether the result is a URL, binary file, or another data shape.
- Connect the result to the next step. Once you know the actual output shape, map the appropriate value into a destination or processing action. Activepieces says Browserless can be combined with other apps, but does not document a particular storage action or mapping for the screenshot result.
Configure only what the current action exposes
Because the public integration listing identifies the action’s field count but not its schema, the reliable configuration reference is the action panel in the version of Activepieces you are using. This matters in both cloud and self-hosted installations: labels or available controls can change over time, and the integration page reported an August 2026 update. Treat that date as a version marker, not as a guarantee that every installation displays identical fields.
- Target website: enter the site address using the format indicated by the current field. If the site is private or requires a session, first check whether the action offers a supported way to supply authentication; do not infer that it can reuse your Activepieces or Browserless login.
- Capture settings: use only options actually present in the action. The reviewed public listing does not establish specific viewport dimensions, wait behavior, full-page behavior, image type, or page-interaction controls.
- Result handling: inspect a successful test run and identify exactly which output contains the screenshot or its reference. Map that output into the next step rather than assuming a filename, binary property, or hosted link.
If an important setting or output is not visible or explained, consult the current Browserless connection instructions or Activepieces’ piece documentation before building downstream logic around it. A guessed mapping can make a flow appear to run while leaving no usable image at the destination.
Choose where the flow runs
Activepieces says the Browserless piece can run on Activepieces cloud or in a self-hosted deployment. It also says the piece is included on every plan, including its free cloud tier and self-hosted deployments. Those are vendor statements about availability; confirm current plan and deployment details for your own account before depending on them in a production workflow.
For either deployment, the key operational dependency is the Browserless connection. Make sure the credential is available to the flow in the selected environment, and test the flow there rather than assuming a connection configured in one environment automatically exists in another. Activepieces also describes the piece as available through its MCP server for agent use; that is an optional agent-oriented path, not a prerequisite for a conventional builder flow.
Other Browserless actions you can combine with a capture
The Browserless piece lists four other actions alongside Capture Screenshot:
- Generate PDF
- Scrape URL
- Run BQL Query
- Get Website Performance
These names may suggest useful steps for a larger automation, but they do not establish their detailed inputs, outputs, or when they are appropriate. Add one only when your workflow needs that operation, then verify its schema and output in the current builder. A screenshot flow does not need all five actions.
Recommended Free Tools
Keep flow screenshots separate from Playwright test screenshots
Activepieces documents another screenshot use case in its engineering playbook for end-to-end tests. That guide uses Playwright and calls page.screenshot() to save an image for debugging tests. This is developer test instrumentation: a screenshot helps diagnose what a browser test saw when it ran.
That is different from using Browserless’ Capture Screenshot action in an Activepieces flow. Use the Browserless action when the screenshot itself is part of an automation workflow. Use the Playwright approach when you are writing or maintaining browser tests and want a debugging artifact. The E2E guide’s example is not a substitute for configuring the Browserless piece, and the integration listing is not a Playwright testing tutorial.
Troubleshoot the capture
The available integration description does not publish a definitive error catalogue. Start with the failed step’s run details and current connection/action help; the checks below address likely workflow-level failure points without assuming undocumented Browserless behavior.
- The action cannot connect: reopen the Browserless connection and review the current Custom auth form. Confirm the credential value with Browserless’ account instructions. The Activepieces listing reviewed here does not identify the required credential field or token format.
- The flow runs but no screenshot reaches the next step: inspect the Capture Screenshot output in that run and remap the actual returned field. Do not assume that the output is an image URL or a binary object; the listing does not specify its structure.
- A field or option in a tutorial is missing: use the current builder’s displayed action schema. The public listing confirms 13 fields, but does not name them; a field set described elsewhere may refer to a different version or setup.
- The target page does not appear as expected: verify that the target address is correct and that the page is accessible under the connection and settings you configured. The reviewed listing does not establish compatibility with protected, authenticated, or dynamic websites, nor does it promise a particular wait or rendering behavior.
- The capture works manually but not in the full flow: test the Browserless step on its own, then inspect the trigger data and downstream mappings. This separates a capture or connection issue from a missing value or mapping in another flow step.
- A self-hosted flow behaves differently from cloud: verify that the connection is configured in the environment actually executing the flow and review that deployment’s current piece setup. Activepieces says both deployment choices are supported, but that does not guarantee identical local configuration.
Or skip the browser setup
If you need a direct screenshot API call rather than a Browserless step inside Activepieces, ScreenshotNeo offers a one-request capture. For example, this cURL command saves a WebP screenshot of Stripe:
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 & 11curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpReplace the example URL with the page you want to capture and provide your ScreenshotNeo API key. See the ScreenshotNeo API documentation for request details. ScreenshotNeo is not the Browserless piece and this call does not configure an Activepieces flow; use it when a direct API request suits the job.
ScreenshotNeo removes cookie banners, newsletter popups, and chat widgets before the capture. Bot checks, blank pages, and failed loads are never billed. It also has an MCP server that lets AI agents take screenshots. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000. Sign up for ScreenshotNeo free.
What is established—and what to verify
Activepieces’ official Browserless integration page establishes the no-code action route, Custom auth, the named action, and the adjacent actions. It describes the piece as combinable with 760+ other apps, a vendor claim rather than an independent measure. The page reported an August 2026 update, so field labels and availability are worth checking in the version you use. The official E2E Tests playbook establishes the separate Playwright debugging example.
The reviewed pages do not establish the Capture Screenshot fields’ names or semantics, output format, dimensions, storage behavior, price of Browserless, or performance on particular sites. If your workflow depends on any of those specifics, confirm them in the current builder or current Browserless documentation before building around them. This avoids treating a high-level integration description as a complete technical schema.
Frequently Asked Questions
Does the Browserless piece start an Activepieces flow by itself?
The integration listing reports zero triggers for the piece. Set up a separate flow trigger appropriate to your automation.
Can I use this method to save screenshots from a Playwright test?
The Browserless action is a flow step. For Playwright test debugging, Activepieces’ E2E guide shows the distinct `page.screenshot()` approach.
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.
