How to Create a Website Screenshot Workflow in Activepieces

To capture a website in an Activepieces flow, add the Browserless piece, connect it using the Custom auth option, and choose Capture Screenshot. Configure the fields shown in your current builder, run a test, and inspect the returned output before mapping it into storage or another action. The public listing does not specify the credential format, exact field names, result schema, or storage behavior, so use the live connection form and test output as the source of truth.

Activepieces’ Browserless listing describes five actions and zero triggers; Capture Screenshot is listed with 13 fields. Those counts describe the listing and may change. The piece is listed for Activepieces Cloud and self-hosted deployments.

1. Decide how the flow should start and where the image should go

Browserless is an action step, not the flow trigger in the listing. Pick the event that should cause a capture, then decide what the resulting image should do. For example, a flow might take a screenshot after an event from another app and pass the result to a storage, notification, or record-keeping step.

Choose a trigger that matches the job, such as an event in another connected app or a schedule available in your Activepieces setup.
Choose a destination or next action before you configure downstream mappings. The best destination depends on whether people need to view the image, keep an archive, or process it further.
Start with one known, accessible page so you can separate connection and mapping issues from problems with a particular site.

Activepieces says its pieces can be combined with other apps in a flow. The Browserless listing does not guarantee a particular output format or storage destination, so plan to inspect a real test run before completing the mapping.

2. Add Browserless and configure Capture Screenshot

Create or open a flow in the Activepieces builder.
Add Browserless as an action step. If it is not visible, check the piece catalog available to your Activepieces instance.
Create or select a connection. The listing labels authentication Custom auth. Follow the credential instructions in the current connection form and Browserless account flow; the listing does not identify which secret or value belongs there.
Select Capture Screenshot.
Fill in the target page and any capture settings presented by the builder. The listing reports 13 fields but does not publish their names or meanings. Use the current field labels and descriptions rather than assuming options from a different Browserless interface.
Save the step and run a test with a page you can access.

Do not paste credentials from an unrelated Activepieces piece-authoring example. Those examples show how a developer can define authentication for a sample action; they do not document Browserless account setup.

3. Inspect the result and map it into the next action

Open the completed test run and inspect the Capture Screenshot step’s output.
Determine whether the result is a file reference, URL, encoded content, or another structure. Do not assume a value name or file representation that the integration listing does not document.
In the next action, select the actual output field using Activepieces’ data picker, or map the matching path shown in the test output.
Test the complete flow and confirm the destination can use the mapped value. Check that a saved image can be opened and has the expected page and dimensions.
Only then enable the trigger or schedule for regular use.

Activepieces’ general output schema documentation explains how action output can be presented in the builder. It is not a Browserless-specific output contract. The action’s observed result in your run is what should drive your mapping.

4. Choose the right deployment and adjacent Browserless actions

The Browserless listing says the piece can run on Activepieces Cloud or a self-hosted deployment. Choose based on where your team wants its automation and connections to run. The reviewed listing does not provide a detailed cost, security, or performance comparison between those deployment choices.

Capture Screenshot is the relevant action for an image. The same piece also lists Generate PDF, Scrape URL, Run BQL Query, and Get Website Performance. Add one of those only when the workflow needs that specific output; a basic screenshot flow does not require chaining all five.

For a separate, code-oriented repository workflow, shot-scraper’s documentation describes taking screenshots from configuration and automating captures through GitHub Actions. It is an alternative pattern for teams already working in a code repository, not a step inside Activepieces. Its documented default browser window size and selector capture options belong to shot-scraper; they are not Browserless settings.

5. Or skip the browser setup

ScreenshotNeo provides a website screenshot API and MCP server. Use its one-call API when you want an image without configuring the Browserless browser connection and downstream image handling in an automation.

Read the ScreenshotNeo API documentation alongside these examples. Replace the sample target with the page you want to capture and use your API key.

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

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)

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);

ScreenshotNeo removes known cookie and consent banners, newsletter popups, and chat widgets before the shot; each cleanup step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and response headers report the page verdict and billing status. Its MCP server provides screenshot, page-info, and PDF tools for AI agents. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000.

6. Troubleshooting

Symptom	Likely cause	What to do
Browserless is missing from the piece selector	The catalog available to this workspace or installation does not show it.	Search the current catalog and check the Activepieces version or deployment’s available pieces.
The connection cannot be saved or the action reports an auth error	The value does not match what the live Custom auth form expects, or the credential is invalid.	Reopen the connection form and follow its current instructions. Do not infer the credential format from the listing.
The action fields differ from a tutorial	The public listing does not enumerate the 13 fields, and piece fields can change.	Use the field labels and descriptions in the installed builder. Configure only options relevant to the target capture.
The screenshot step succeeds but the next step has no usable image	The downstream mapping assumes a URL or file shape that the action did not return.	Inspect the test output and map its actual value. Check the next action’s accepted input type and test again.
The page capture is blank or incomplete	The page may not have rendered the expected content by the time capture occurred, or the page itself may be inaccessible.	Try a page you control, verify it loads in a browser, and review any wait or capture options actually present in the Browserless action.
The flow works in a test but not when enabled	The trigger context or later app connection may differ from the test run.	Inspect the failed run and confirm trigger data, connections, and mapped output in the published flow.

7. Reliability, performance, and cost

Test representative pages: a simple public page confirms the basic wiring; test pages with the content and access conditions your real workflow depends on before relying on it.
Keep the flow observable: inspect failed runs and retain enough run output to diagnose whether the connection, capture, or downstream mapping failed.
Avoid brittle mappings: map from the current action output and recheck it after changing the piece or its configuration.
Keep credentials in connections: use the builder’s connection mechanism rather than placing secrets in page URLs or downstream messages.
Plan for changing pages: page layout, access requirements, and rendered content can change. Verify important captures periodically.
Confirm plan and resource limits: the reviewed integration listing does not establish Browserless quotas, per-capture costs, latency, or retry guarantees. Check current Browserless and Activepieces account details before estimating production volume.

FAQ

Does Browserless start the Activepieces flow?

The listing shows zero Browserless triggers. Use another flow trigger, then run Capture Screenshot as an action.

Do I need to add all five Browserless actions?

No. Choose Capture Screenshot for an image. The other actions address PDF creation, scraping, BQL queries, and performance analysis.

Can I use the workflow with self-hosted Activepieces?

The listing says Browserless is available with Activepieces Cloud and self-hosted Activepieces. Check the catalog and connection form in your own installation.

What exact property should I map to storage?

The public listing does not specify the result schema. Run the action and inspect its output in your builder before choosing a property.