Connect the Decodo Web Data API to Zapier to fetch web pages, run SERP searches, and run e-commerce searches. Pass page content or structured data to the next step in your Zap, with no code required.
The integration provides three actions backed by the same API. Decodo handles proxy rotation, JavaScript rendering, and bot protection so you can build web scraping automation around the data you need. Retrieval still depends on the target page and the action's time limit.
Test your target and settings in the Decodo Playground before building a Zap. The options exposed in Zapier are listed below.
| Action | What it does |
|---|---|
| Fetch URL | Scrapes one page and returns Markdown, HTML, or a PNG screenshot. |
| Fetch URL List | Scrapes up to 25 URLs per run and returns each page's content, plus counts and failure details. |
| Run Search | Runs a SERP or e-commerce search and returns parsed results or page content. |
Fetch URL and Fetch URL List return Markdown by default. Both expose location, device type, and headless rendering settings. Choose rendered HTML to read content that appears after JavaScript runs, or turn Markdown off to capture a screenshot.
Run Search exposes different settings for each search type:
| Search type | Required input | Optional settings |
|---|---|---|
| Search SERP | Search query | Parsed results, Markdown, headless rendering, location, and locale |
| Search E-Commerce | Search query | Parsed results, Markdown, headless rendering, location, and regional domain |
Search SERP and Search E-Commerce return parsed results by default. Turn Return parsed results off to get page content, then choose HTML, Markdown, or a screenshot.
- Search results in a spreadsheet. Use Run Search to collect SERP or e-commerce results, then map the returned fields into spreadsheet rows.
- Web content for an AI step. Fetch a page as Markdown and pass its content to a summarization or analysis step.
- Data extraction from a URL list. Map URLs from an earlier Zap step into Fetch URL List, then process the returned content and route failed URLs for review.
- Rendered or location-dependent pages. Enable headless rendering for JavaScript content or choose a location to retrieve a page from a specific country or city.
- Create an account on the Decodo dashboard.
- Copy your Web Data API key from your Web Data API subscription on the dashboard.
- Add a Decodo action to your Zap after your chosen trigger. Select Fetch URL, Fetch URL List, or Run Search, then connect your account using the API key.
- Configure the action with a URL, a URL list, or a search query. Choose the output and any additional settings you need.
- Test the step and inspect the result, then map the returned data into your next Zap step. For URL lists, check the failure count and reasons as well as the fetched content.
The integration uses a Web Data API key from your subscription on the Decodo dashboard. Enter it in the API Key field when connecting your Decodo account in Zapier.
Zapier checks the key with Decodo when you connect. If the key is rejected, check it in the dashboard and reconnect the account.
- Timeouts. Each API request has a 25-second timeout. The entire action must finish within Zapier's 30-second action limit, including a URL list run. If requests time out, try fewer URLs or turn off Headless.
- Bulk limits. Fetch URL List accepts at most 25 URLs per run and scrapes up to 10 at a time. The integration applies an output cap of roughly 5 MB. Results beyond that cap appear in the failure list with a reason, even if the page was fetched successfully.
- Partial success. A URL list run with at least one returned result counts as a success.
Check
scraped,failed, anderrorsbefore processingresults. A run with no returned results fails. - Search output. Both search types support parsed results and headless rendering. Markdown applies only when parsed results are off.
- Screenshots. A screenshot returns a PNG in place of page content. Turn Markdown off for either URL action. For a search, turn both parsed results and Markdown off, then select Screenshot (PNG) under Headless.
- Actions only. The integration provides actions, with no triggers. Choose a trigger from another app or use a Zapier schedule to start your workflow.
Install, build, and check the integration
From the repository root:
npm install
npm run build
npm test
npm run lint
npm run format:checknpm test builds the integration before running the tests. The current tests mock API requests
and do not require a Decodo API key. Use npm run format to apply formatting to the source files.
The actions live in src/creates/, their input fields in src/input-fields.ts, and request and
batch limits in src/constants.ts.
- Web Data API documentation
- Decodo dashboard
- Decodo Discord
- Decodo CLI & MCP server for scraping outside Zapier