- Home
- Resources
- Integrations
- Oxylabs
Oxylabs Zapier integrationAutomate Oxylabs with Zapier.
The Oxylabs Zapier integration gives you 0 triggers, 4 actions and 0 searches. Oxylabs never starts a Zap: another app does, then Oxylabs fetches a page, an Amazon product or a results list and hands the data to the next step.
Verified Trustpilot reviews · AI, automation & growth agency
What the Oxylabs Zapier integration does for you
The Oxylabs Zapier integration lets any of your apps order a scrape without code. Something happens elsewhere, a new row or a form entry, and Oxylabs goes to fetch a web page, an Amazon product or a list of search results. What it brings back feeds the rest of the Zap.
Three outcomes worth building, each on a real action:
A product sheet that fills itself. Drop an Amazon product id in a spreadsheet and Scrape Amazon Product fetches that product page, so the row gets the data your team would otherwise copy by hand.
A watch list on search results. Search on Google or Search Products on Amazon runs the query you pass it, and the results land wherever your team reads them.
A snapshot of any page. Scrape Any Url takes a direct link and returns the page, ready to store or to pass to the next step.
What Zapier does not do here: Oxylabs has no trigger, so it cannot start a Zap on its own or tell you when a page changes. Each scrape happens because another app's trigger fired. There is no search step either, despite two actions having "Search" in their name: those are actions, and they count as tasks.
Oxylabs also has a page in our Make catalog: Oxylabs Make integration. For the broader choice, see Make vs Zapier.
Zapier vocabulary in one minute
Seven terms, one line each, reused as-is in the rest of the page.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run every time that event happens.
- Trigger
- The event that starts the Zap. Oxylabs has none, so it always comes from another app, like a new spreadsheet row.
- Action
- What the Zap does once started: the step that writes, sends or fetches something for you. All four Oxylabs operations are actions.
- Task
- The unit Zapier bills: one action your Zap completes successfully. Each Oxylabs scrape that works counts as one.
- Polling vs instant
- A polling trigger is checked on a timer; an instant one is reported by its app straight away. Here, it depends on the app that starts the Zap.
- Filter
- A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
- Connection
- Your Oxylabs account linked to Zapier once, then reused by every Oxylabs step in every Zap.
What an Oxylabs Zap really costs
Oxylabs is not a premium app: it runs on the free plan.
- Premium appNo, free plan works
- Free plan100 tasks a month, two-step Zaps
- Each successful scrape1 task
- Oxylabs triggers0, another app starts the Zap
The trigger of the other app never costs a task. Each Oxylabs action that succeeds counts as one, and one that fails is not counted. The free plan gives 100 tasks a month and unlimited Zaps, with two steps per Zap: a trigger and one action. Scraping and then writing the result somewhere is already three steps, so a multi-step Zap and a paid plan. If the starting trigger polls, the grid below sets how often it checks.
Connect Oxylabs to Zapier in three steps
- 01
Open your connections
In Zapier, go to the Apps page and click + Add connection. You need an Oxylabs account first, plus access to anything you do not own yourself but want the Zap to use.
- 02
Pick Oxylabs
Search for Oxylabs by name in the dialog, select it, then click Add connection. A new tab then opens on the Oxylabs sign-in screen, right next to Zapier.
- 03
Sign in and allow access
Log in to Oxylabs in that tab and grant Zapier access to the account. The connection lands in your list, and every Oxylabs step you add later reuses it.
Your first Zap: enrich a product list from Amazon
GoalEach Amazon product id added to a sheet gets its product data scraped and written back next to it.
- 01
Set the trigger
Start a new Zap with Google Sheets and New Spreadsheet Row on the sheet where your team lists Amazon product ids, one per row.
- 02
Test with a real row
Run the trigger test. Zapier brings back the three most recent rows, so pick one with a product id and build the next steps on it.
- 03
Add the scrape
Add Oxylabs, choose
Scrape Amazon Product, and map the product id from the row into Query. Switch Parse on if you want structured data back. - 04
Write the result back
Add Google Sheets again with Update Spreadsheet Row and map what Oxylabs returned into the columns you keep for it in that row.
- 05
Test, then publish
Test each step and read what came back before going further. Then click Publish. With three steps, this Zap is multi-step and needs a paid plan.
The 4 Oxylabs actions
Oxylabs gives you 4 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Scrape Amazon Product
ActionIn Zapier“Scrape results from Amazon product pages”
Fetches one Amazon product page from its product id and hands what it found to the next step.
Scrape Any Url
ActionIn Zapier“Scrape any website url”
Grabs whatever page sits behind a direct link you give it, from any website.
Search Products on Amazon
ActionIn Zapier“Scrape results from Amazon search”
Runs a search on Amazon with the words you pass and brings back the list of products that come up for them.
Search on Google
ActionIn Zapier“Scrape results from Google Search”
Sends a query to Google and brings the results back into your Zap for the next step to store or sort.
When an Oxylabs Zap breaks
Zapier attaches no help article to Oxylabs and lists no limit specific to it. What goes wrong comes from Zapier's own rules and from the inputs you feed the scrape.
Four cases cover most failures. If the cause is still unclear, our Zapier troubleshooting page goes further.
Old rows are never scraped
A Zap only reacts to what happens after it is switched on. Product ids already in the sheet are not picked up; scraping that backlog is a separate job.The sheet keeps setting off the Zap
Writing the scrape result into the same place the trigger watches can start the Zap again and again, and it burns through tasks fast.A bulk paste gets held back
Pasting a huge batch of ids at once can trip Zapier's flood protection, which holds the trigger back instead of scraping every row.The step stops on an empty Query
Query or Url is required on every Oxylabs action. A row or form entry without that value leaves the scrape with nothing to fetch.
Need help automating Oxylabs with Zapier?
A person reads every message.



