Workflows
Each one below chains the same shipped primitives (fetch, extract, batch, browser sessions) into a single repeatable task instead of a script you maintain by hand. Open a card to see the real commands: some run as-is today, others are patterns you adapt to your own data.
Each workflow turns a recurring web-data task into something that runs on its own, built from primitives your team already has access to. Open a card to see exactly what it does before you commit engineering time to it.
Gather competitor pages, extract structured data, keep it fresh on your own cron or CI.
Ships in the CLI today, requires protected_fetch + extract.
zenrows workflow explain competitor-intelligence
CSV in, enriched CSV out, or land it directly in HubSpot, Salesforce, or Clay.
Compose it yourself: extract, looped over each row of your CSV.
zenrows extract <url> --autoparse
Product catalogs at scale (variants, reviews, prices, images) into your stack.
Compose it yourself: batch, one job per catalog pass.
zenrows batch create jobs.jsonl --wait
When another tool fails on a protected site, check what Zenrows can do and get a working command.
Compose it yourself: check status, then fetch with the right flags.
zenrows status
A working Zenrows equivalent for any Playwright or Puppeteer scraper, with cost comparison.
Compose it yourself: swap page.goto() for a single fetch call.
zenrows fetch <url> --js-render
Adjacency
Different audience. Different shape. Same outcome. Cross-linked, not duplicated.
Workflows are commands your agent can run, or patterns your team can build. Solutions are outcomes for your buyer. Different surface, same problem.
Browse SolutionsWorkflows live in the open-source toolkit, ready to run the moment your agent needs one.
Every workflow ships as a landing your team can read, and a real pattern your engineers can build from using the same primitives, ready when they need them.