--- title: "Oxylabs Integration" description: "Give AI agents web data collection at scale through the Oxylabs Scraper API. Agents scrape any URL or dedicated targets like Google and Amazon with JavaScript rendering and structured parsing, and run large crawls as asynchronous batch jobs they poll to completion." url: https://flowrunner.ai/integrations/oxylabs date_modified: 2026-08-01T02:40:32-07:00 --- # Oxylabs [Developer Tools](https://flowrunner.ai/integrations/category/developer-infrastructure) Give AI agents web data collection at scale through the Oxylabs Scraper API. Agents scrape any URL or dedicated targets like Google and Amazon with JavaScript rendering and structured parsing, and run large crawls as asynchronous batch jobs they poll to completion. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 5 actions · Basic auth · available [Oxylabs website](https://oxylabs.io/) · [Platform Documentation](https://developers.oxylabs.io/) · Capability data verified 2026-08-12 1. The nightly marketplace monitoring window opens on schedule 2. Submit Batch Jobs queues one amazon\_product job per tracked ASIN with structured parsing enabled 3. Get Job Status polls the batch until every job reports done, with faulted jobs collected for retry 4. Get Job Results pulls the structured product JSON, price, availability, and rating, for each ASIN 5. The agent diffs prices and availability against yesterday's snapshot and flags every change 6. The category manager reviews the flagged changes before any repricing rule or listing update fires 7. The morning digest posts to the channel with movers ranked and faulted jobs listed for the record ## What This Integration Enables Oxylabs is web data collection at industrial scale: a scraper API backed by a proxy network that handles JavaScript rendering, geo-localization, and the adversarial reality of scraping sites that do not want to be scraped. The dedicated sources are the difference in kind. Pointing google\_search or amazon\_product at a query returns structured JSON, parsed by scrapers maintained against those exact page layouts, which turns the most volatile part of scraping, the parsing, into someone else's full-time job instead of yours. FlowRunner agents run the full lifecycle. Quick lookups go through the synchronous endpoint; large crawls run as asynchronous batches the agent submits, polls, and collects without a human babysitting the queue. - Scrape (Realtime) answers short requests in one call, with rendering, parsing, and geo\_location options - Submit Scrape Job (Async) handles slow or heavy targets that would blow past a synchronous timeout - Submit Batch Jobs fans one configuration across hundreds of keywords, ASINs, or URLs, each as its own trackable job - Job statuses progress through pending, processing, done, and faulted, so flows branch on outcomes instead of guessing - Batch scope and spend run through [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) authorization before submission ### Without FlowRunner **Big crawls are engineering projects**: Anything past a few hundred pages means proxy pools, retry logic, and a script someone has to own **Marketplace pages fight back**: JavaScript rendering, geo-restrictions, and layout changes turn simple price checks into maintenance **Crawl spend is discovered on the invoice**: Jobs launch from cron with nobody sizing the run, and the metered bill explains it later ### With FlowRunner **A crawl is a batch job with a lifecycle**: Submit, poll, collect: thousands of pages run as governed jobs with statuses a workflow can act on **Dedicated sources return data, not HTML**: Google and Amazon targets come back as structured JSON, parsed by scrapers built for those pages **Scope is approved before submission**: Large batches state their job count and options up front, and a person signs off before the meter runs ## Use Case Scenarios ### Marketplace prices watched at catalog scale An e-commerce team tracks its full ASIN list. Nightly, the agent runs Submit Batch Jobs against amazon\_product with parsing on, polls to completion, and writes price, availability, and rating per ASIN to [Google Sheets](https://flowrunner.ai/integrations/google-sheets). The diff against yesterday drives the morning digest in [Slack](https://flowrunner.ai/integrations/slack): who moved, who went out of stock, whose rating slid. Repricing decisions stay with the category manager, made from data that was collected while the team slept. ### Search visibility tracked like a metric, not a ritual Marketing tracks a keyword set across markets. The agent submits google\_search jobs per keyword with geo\_location set per market, parses the structured SERP results, and records where the company and its competitors rank. Week-over-week movement posts to the channel; a competitor suddenly outranking the company on a money keyword pages the SEO lead the same morning. The rank-tracking subscription becomes a workflow the team controls end to end. ### JavaScript-heavy sources turned into structured records Competitor dealer locators and careers pages render entirely client-side. The agent uses Scrape (Realtime) with Render enabled through the universal source, passes the resulting HTML to an extraction model for structured fields, and appends new locations and job postings to the market intelligence base in [Notion](https://flowrunner.ai/integrations/notion). Expansion signals, new cities, new sales roles, surface as weekly deltas a human analyst reviews, instead of quarterly surprises. ## Human-in-Loop Highlight Submit Batch Jobs is the commitment on this page: one call can queue thousands of jobs, each metered, each rendering and parsing on Oxylabs infrastructure, and once the batch is submitted the spend is spoken for. A loop that resubmits a batch on a malformed condition, or an agent that expands "tracked ASINs" from eight hundred to eighty thousand because an input sheet changed shape, commits real money at API speed. So batch submission is gated on scope. The agent assembles the run and presents it: "Nightly price sweep ready: 1,240 amazon\_product jobs, parse enabled, no rendering. Yesterday's run was 1,238. Submit?" A batch that suddenly triples gets a question instead of a submission. The same review covers option changes that multiply cost, enabling JavaScript rendering across a whole batch is a different bill than parsing alone. Collection runs at whatever scale the job needs; the decision to run at that scale is made by someone who can read an invoice. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 5 actions ### Scraping 5 - **Scrape (Realtime)** Submits a scraping job and returns results synchronously in one request. Takes a source, universal for any URL or a dedicated scraper such as google\_search, amazon\_search, or amazon\_product, with optional JavaScript rendering, structured parsing on supported targets, geo\_location, and user agent type. Best for short-running requests. - **Submit Scrape Job (Async)** Submits a job through the Push-Pull endpoint, returning a job id with pending status immediately. Accepts the same source, rendering, and parsing options as the realtime action, plus an optional callback URL Oxylabs notifies on completion. The path for large, slow, or many-page targets. - **Get Job Status** Retrieves an asynchronous job's status and metadata as it progresses through pending, processing, done, or faulted. The polling step; it does not return scraped content. - **Get Job Results** Retrieves a completed job's output: raw HTML or structured JSON when parsing was enabled, with the final URL and HTTP status per scraped page. Returns full content only after status reports done. - **Submit Batch Jobs** Submits many jobs in one request from shared parameters and a list of queries or URLs, each entry becoming its own trackable job id. The scale lever for keyword sets, ASIN lists, and URL inventories, and the operation this page's human gate sizes before submission. ## Frequently Asked Questions ### What can FlowRunner do with Oxylabs? FlowRunner agents can run Scrape (Realtime), Submit Scrape Job (Async), and Get Job Status in Oxylabs, plus 2 more actions. ### Does connecting Oxylabs to FlowRunner require OAuth? No. Oxylabs connects to FlowRunner with basic authentication (a username and password), no OAuth flow required. ### Can Oxylabs trigger a FlowRunner workflow automatically? Oxylabs doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Oxylabs?** This integration exposes Oxylabs to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/oxylabs. Site index: https://flowrunner.ai/llms.txt