Define the permitted source and output
Choose pages you are authorized to automate, list the fields to collect, select a stopping rule, and define the Excel columns before capturing elements.
WEB DATA EXTRACTION WORKFLOW
Collect structured web data and save it to Excel.
This workflow pattern reads repeated cards or rows, extracts selected fields, follows pagination, validates the results, and writes a clean spreadsheet—using visual steps you can inspect and edit.
GOAL AND OUTPUT
Define a reliable data contract before automating clicks.
Start by naming the exact fields you need—for example, product name and displayed price—and the output columns that will receive them. Decide whether an empty field should skip the row, produce a blank cell, or stop the run for review.
The workflow should also define a stopping rule: a disabled next-page button, no next-page element, a maximum page count, or a repeated URL. Clear rules prevent an accidental infinite loop and make the final record count explainable.
Responsible use: automate only pages and data you are authorized to access. Follow the website’s terms, access controls, robots guidance, rate limits, and applicable privacy and data laws.
VISUAL WORKFLOW
Six steps from webpage to spreadsheet.
AI can draft this structure from a plain-language request. Review the generated elements, variables, limits, and output path before the first full run.
Open or attach to the webpage
Open the starting URL or connect to the current browser tab, then store the webpage object for all later browser commands.
Capture the repeated item
Capture one representative card or row and configure a similar-elements command to return the complete collection on the current page.
Extract and validate fields
Loop through the items, read related name and price elements, normalize text, reject empty records, and add valid rows to an in-memory collection.
Handle pagination explicitly
After processing a page, locate the next-page control, stop normally when it is absent or disabled, otherwise navigate and wait for the new collection to load.
Write the verified result to Excel
Create or open the destination workbook, write a header and rows, save the file, and log the record count, page count, destination, and duration.
BOUNDARY CASES
Test the assumptions hidden in the page.
No results
Treat an empty result set as a valid outcome when appropriate. Create the workbook with headers, log zero records, and avoid entering a pagination loop.
Missing optional fields
A card may have no price, badge, or secondary text. Decide field by field whether to keep the row with a blank value or discard it. Do not let one optional element abort the entire page.
Duplicate or sponsored items
Choose a stable identifier or a combination of fields for deduplication. If promoted items should be excluded, make that filter visible in the workflow rather than cleaning the spreadsheet manually afterward.
Long text and special characters
Preserve Unicode text, trim unwanted whitespace, and test names containing quotes, commas, currency symbols, emoji, and line breaks. Spreadsheet cells should receive values—not formulas constructed from untrusted page text.
PAGINATION FAILURES
Make “no next page” different from “selector broke.”
Final page
The absence of an enabled next-page control is an expected stop condition. Log completion and save the data already collected.
Changing attributes
A captured locator may contain a page number such as an accessibility label that changes from “page 2” to “page 3.” Prefer stable attributes and relationships, then test the locator on multiple pages.
Slow or partial loading
Wait for a meaningful page signal instead of using only a fixed sleep. Validate that the new collection differs from the previous page before continuing.
Navigation does not advance
Store the previous URL or a page signature. If clicking Next does not change it within the expected time, stop with a diagnostic error instead of collecting the same page forever.
VERIFICATION
Prove the output before scaling the run.
Begin with one page and compare several rows against the source. Then test two pages, the final page, an empty result, a missing optional field, a slow page, and a deliberately broken locator.
Verify that the workbook opens, headers appear once, row counts match the accepted records, special characters remain intact, and the file is saved to the expected path. Logs should make it possible to reconcile each page count with the final total.
Where AI helps: use the assistant to draft the visual workflow, explain each command, add boundary handling, or inspect the flow and runtime evidence after a failure. Once approved, ordinary browser, loop, validation, and spreadsheet commands run without repeated model calls.
Generate the first draft, then refine every detail.
Change the target website, captured fields, stopping rule, validation, spreadsheet path, and error policy in the visual editor.