Unlike one-click, bulk extraction, collecting data with multiple commands is designed for more complex scenarios that require additional interactions beyond simply pulling data from a list. If your task involves not only harvesting data from a list but also performing actions on each item—such as opening detail pages, applying filters, or filling out forms—sequential collection is the right tool for the job.
The core idea and when to use it
Sequential data collection defines a method where you manually string together basic commands to create a tailored automation flow for data gathering. It is especially useful when you need to go beyond bulk extraction to include per-item interactions. For example, imagine a product list where you must click into each product’s details, assess certain conditions, and then save the results. In such cases, a single batch extraction won’t cover the required steps, and a line-by-line approach becomes essential.
Three essential building blocks you’ll rely on
At the heart of sequential collection are three commands that work in concert to process each item in a list:
This command identifies a list on a web page—such as a product grid or search results—and automatically iterates through each item. Its primary role is to establish the “current item” you are working on within the loop. Think of it as the mechanism that marks a new target item for every iteration.
Inside the loop, this command uses the current item as a reference to locate related elements within the page structure. The most common use is to find a sub-element inside the current item, such as the title, price tag, or a specific button. It provides precise access to the parts of the item you need to interact with or evaluate.
From the located sub-element, this command extracts the exact information you require—text content, URLs, attribute values, and more. The data you obtain can be saved directly or used to guide decision-making in a conditional step within your workflow.
How the basic workflow comes together
A typical sequential collection pipeline follows a clear sequence:
Establish the loop: Use
Loop through similar web elementto identify the entire target list. This creates the framework for processing each item one by one.Narrow to the specific area: Inside the loop, apply
Get relative elementon web page to pinpoint the exact sub-elements within the current item that you need to inspect or interact with.Extract and decide: Use
Get details of element on web pageto pull out the necessary data from the sub-elements. You can store this information directly or feed it into conditional logic (an If statement) to determine the next steps.Act or save: Based on your decision logic, perform required actions—such as clicking through to a detail page, performing additional interactions, or collecting results into a structured output. Finally, you may use a Write to row-like operation to save the gathered data in a spreadsheet or database.
Putting it all together for a practical task
Imagine you’re automating the process of collecting product information from a listing page. You begin by looping through every product in the grid with Loop similar web element. Within each product, you locate the title and price using Get relative element on web page. Then you extract the text via Get details of element on web page. You may apply a condition such as “if price is under a certain threshold” or “if the product has a discount,” and based on that, you might click to open the detail page or skip the item. Finally, you save the relevant data with Write to row, compiling a clean dataset for further analysis.
Why this method is valuable
The sequential approach offers flexibility for complex automation that demands per-item decisions and interactions. By first capturing the list with a loop, you ensure you consistently work on the correct item. Then, by progressively locating sub-elements and extracting details, you gain precise control over what you collect and how you respond to it. This structure makes it easier to handle pages with intricate layouts or conditional requirements, and it scales well to various use cases where simple bulk extraction falls short.
A final note on design and best practices
When building a sequential data collection workflow, plan your steps with clarity: define the target list, map the critical sub-elements you need to interact with, and determine the exact data you’ll extract at each item. Keep interactions modular and readable, so future adjustments—such as changing locator strategies or adding new conditions—are straightforward. Start small with a single page and a few items, then expand gradually to ensure reliability across different pages and states.
In summary, multi-command data collection provides a practical, modular approach for automating data gathering that requires per-item actions. By looping through items, precisely locating sub-elements, extracting their details, and applying logical decisions, you can build robust workflows that handle complex web interactions while producing clean, actionable results.