What Does BrowserAct Full Page Screenshot Scraper Do?
Use BrowserAct Full Page Screenshot Scraper to collect visible page text and a full-page PNG from one public URL, including meta_description, page_title, language, visible_text, captured_at. The Bot stays within the selected public Public Web page flow and returns structured page capture data for website archiving, visual QA, or downstream automation without writing code or requiring a target-site login. Run it in BrowserAct or invoke the same published template through its API Tab.
Key Features of Full Page Screenshot Scraper
- Configure
page_urlto reuse the same Bot for different public Public Web targets. - Collect visible page text and a full-page PNG from one public URL from the template's defined public page flow.
- Return structured page capture data with fields such as
page_title,meta_description,language,visible_text,captured_at. - Run without a target-site account login or custom scraper code.
- Use the API Tab to connect the same published template to downstream automation.
What Data Can I Extract from Public Web?
| Field | Description |
|---|---|
page_title | Visible page title shown on Public Web. |
meta_description | Visible meta description returned by the public page. |
language | Language returned from the public Public Web page. |
visible_text | Visible visible text returned by the public page. |
captured_at | Captured At returned from the public Public Web page. |
screenshot_file | Screenshot File returned from the public Public Web page. |
How to Use Full Page Screenshot Scraper
Quick Start Guide
1. Open Run Task.
2. Review or change the populated input values.
3. Run the Bot.
4. Review the structured result in the Output Tab.
5. Connect the published template to your downstream workflow when needed.
Input Parameters
| Parameter | Configuration |
|---|---|
page_url | String; required; default https://example.com/. Public page url to process. |
Example Output
The table shows one representative real result. Long text is shortened only in this documentation preview.
| Field | Result |
|---|---|
page_title | Example Domain |
meta_description | null |
language | en |
visible_text | Example Domain This domain is for use in documentation examples without needing permission. Avoid use in operations. Learn more |
captured_at | 2026-09-14T11:57:00Z |
screenshot_file | full-page-screenshot.png |
How Does It Work?
1. BrowserAct validates the supplied inputs and maps supported dropdown selections.
2. The Bot constructs or normalizes the target URL and opens the supplied public detail page.
3. It reads the visible page capture data without entering unrelated pages or account-only areas.
4. It normalizes visible values, preserves valid optional values, and stops after the target page has been processed.
5. The run returns one structured response for review, export, or downstream automation.
How to Build a New Scraper Bot with Agent Built
Step 1: Describe the data you need
Open BrowserAct and start Agent Built from the Home prompt box or from Create > Build with Agent. Describe the public website, records, filters or search conditions, output fields, result limit, and reusable inputs you need.
Step 2: Let BrowserAct build and test the Bot
BrowserAct explores the live website, creates the navigation and extraction workflow, and tests the resulting Bot. Provide any requested clarification about the target page, conditions, fields, or expected output in the same build conversation.
Step 3: Run the Bot and review the result
Run the completed Bot with its populated default inputs. Review the structured records, source URLs, missing optional values, and result count before reusing the Bot with other inputs or connecting it to another workflow.
Use Cases
- Website archiving.
- Visual QA.
- Page content collection.
- Connect the structured result to API clients, n8n, Make, Zapier, MCP-based agents, or supported exports.
Why Use Full Page Screenshot Scraper?
- Reuse a tested public-page workflow instead of configuring the extraction from the beginning.
- Receive structured page capture data that can move directly into research, review, or automation.
- Change supported inputs without rebuilding the Bot for every run.
Who Can Use Full Page Screenshot Scraper?
- Teams working on website archiving.
- Teams working on visual QA.
- Teams working on page content collection.
- Developers and automation teams connecting public web data to downstream systems.
How Many Results Can You Scrape?
Each run processes one selected public target and returns one structured result for that target.
Automation and Export
BrowserAct produces structured data first. Use the result through Run Task, the JSON API, n8n, Make, Zapier, MCP-based agents, or the supported manual export flow.
Need Help?
Cannot find the exact capability you need, or need help composing several Bots?
