Skip to main content
The Decodo Zapier integration connects the Web Data API to your Zaps. Fetch web pages, scrape lists of URLs, or run Google and Amazon searches, then pass the content or parsed results to the next step – a spreadsheet, an AI step, a Slack message – with no code.
View the zapier repository for the source code and latest releases.

​
Actions

The integration provides three actions and no triggers. Start your Zap with a trigger from another app, or with Schedule by Zapier.

​
Setup

  1. Copy your Web Data API key from the Web Data API playground. Any Web Data API plan works. Free trials are available on the dashboard.
  2. In your Zap, add a step and search for Decodo.
  3. Choose Fetch URL, Fetch URL List, or Run Search.
  4. Connect your Decodo account by pasting the API key into the API Key field. Zapier checks the key with Decodo before saving the connection.
  5. Configure the action, test the step, and map the returned fields into your next step.
Try your URL or search in the Web Data API playground first. The settings map directly to the fields in Zapier.

​
Fetch URL and Fetch URL List

Both actions scrape pages with the universal target and share the same settings:
Screenshot (PNG) only appears once Return markdown is turned off.
Fetch URL returns content, url, status_code, task_id, created_at and updated_at. Fetch URL List fetches up to 10 URLs at a time and returns: A run counts as successful if at least one page comes back, so check failed and errors before using results. The run only fails when no page comes back at all. Choose the Search Type first. The other fields depend on it: Search SERP calls the Google Search target, and Search E-Commerce calls Amazon Search. With Return parsed results on, the results come back as structured fields you can map into later steps. Turn it off to get the page itself as HTML, Markdown, or a screenshot – for a screenshot, turn Return markdown off too and set Headless to Screenshot (PNG).
For Search SERP with Return markdown on, leave Headless empty. Google with both Markdown and JavaScript rendering is slow and often fails, while Markdown alone returns in a few seconds.

​
Limits

  • Time limit – each Decodo request has a 25-second timeout, and the whole action must finish within Zapier’s 30-second limit. If a step times out, turn Headless off or fetch fewer URLs per run.
  • URL list size – Fetch URL List accepts at most 25 URLs per run. Split longer lists across several runs.
  • Output size – a URL list run returns about 5 MB of content at most. Pages past that point are listed in errors as left out, even though they were fetched.

​
Example workflows

  • Search results in a spreadsheet – Run Search on a schedule, then map the parsed results into Google Sheets rows.
  • Web content for an AI step – Fetch a page as Markdown and pass content to a summarization or analysis step.
  • Data extraction from a URL list – Map URLs from an earlier step into Fetch URL List, process results, and route errors for review.
  • n8n – Build scraping workflows in n8n’s visual automation platform.
  • MCP Server – Connect AI agents and MCP-compatible tools to Decodo.
  • Web Data API playground – Test targets and settings before building a Zap.

Support

Need help or just want to say hello? Our support is available 24/7.
You can also reach us anytime via email at support@decodo.com.

Feedback

Can’t find what you’re looking for? Request an article!
Have feedback? Share your thoughts on how we can improve.