{ "schema_version": 1, "generated": "2026-10-24", "id": "ggoggam-vitre--fan-out-search-results-to-detail-pages", "repo": "ggoggam/vitre", "repo_url": "https://github.com/ggoggam/vitre", "repo_slug": "ggoggam-vitre", "title": "Visit every search result and collect details from each", "page_title": "How to visit every search result and collect details from each with Vitre", "summary": "Use forEach to open each result page on a lane pool and gather extracted fields in row order.", "who": "A developer building a price or listing monitor who needs detail data for each row a search page produced.", "problem": "Opening many pages one by one in a single WebView is slow, and parallel WebView calls race each other.", "outcome": "A details variable holding one extracted record per item, in row order, with failed items recorded instead of stopping the run.", "steps": [ "Extract the result rows with extractRows into a named variable such as results.", "Add forEach over that variable with an item name such as product and a limit.", "Inside the body, navigate to template(\"{product.url}\"), waitFor the detail element, and add extract steps.", "Provide a LaneSource with more than one lane if you want items to run in parallel, then read the details variable from Completed." ], "agent_prompt": "In , build a Vitre workflow that extracts rows from into results, then uses forEach to visit each row URL and extract . Expected output: a details array in row order with one entry per item. Verify that any failed item appears as a recorded failure rather than aborting the whole run.", "agents": [ "any" ], "difficulty": "Advanced", "time": "2 hours", "basis": "readme", "caveat": "The README says a fan-out is a page barrier, so the step after forEach starts on a blank page with variables intact, and lanes must be configured in your own app.", "category": "Software and DevOps", "tags": [ "Software and DevOps" ], "lang": "kotlin", "requirements": [ "Kotlin 2.3.10 Multiplatform project (Android minSdk 24, iOS 15.0+, or desktop with JetBrains Runtime and JCEF 21)", "Maven Central access, which is the only setup needed for the published artifacts", "Compose Multiplatform if you want the optional vitre-compose UI layer" ], "risk": "dual-use", "seen_in_the_wild": false, "mentioned_publicly": false, "risks": [ { "tag": "account-pooling", "notice": "Running many lanes against the same site may conflict with that site's terms, so check them before fanning out at volume." } ], "best": false, "score": 0.8, "evidence": [], "url": "https://dedupedai.com/use-cases/ggoggam-vitre/fan-out-search-results-to-detail-pages/", "md": "https://dedupedai.com/use-cases/ggoggam-vitre/fan-out-search-results-to-detail-pages/index.md", "disclaimer": "Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked \"Seen in the wild\", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email hello@dedupedai.com and we will look at it promptly.", "api": "https://dedupedai.com/api/v1/usecases/ggoggam-vitre--fan-out-search-results-to-detail-pages.json", "api_version": "v1" }