> ## Documentation Index
> Fetch the complete documentation index at: https://help.decodo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Zapier

> Connect the Decodo Web Data API to Zapier: fetch web pages, scrape URL lists and run Google or Amazon searches inside your Zaps, with no code.

The Decodo [**Zapier integration**](https://zapier.com/apps/decodo/integrations) 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.

> [!NOTE]
>
> View the [**zapier repository**](https://github.com/Decodo/zapier) 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**.

| 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 in one run and returns each page's content, plus counts and failure details |
| **Run Search** | Runs a Google or Amazon search and returns parsed results or page content |

## Setup

1. Copy your Web Data API key from the [**Web Data API playground**](https://dashboard.decodo.com/web-data/playground). Any [**Web Data API plan**](https://dashboard.decodo.com/web-data/pricing) works. Free trials are available on the [**dashboard**](https://dashboard.decodo.com/).
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.

> [!TIP]
>
> Try your URL or search in the [**Web Data API playground**](https://dashboard.decodo.com/web-data/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:

| Field | Default | Description |
| - | - | - |
| **URL** / **URLs** | – | The page to fetch, or up to 25 pages. Required. For a list, add one URL per row or map a comma-separated list from an earlier step |
| **Return markdown** | On | Return clean Markdown instead of raw HTML. Best for passing content to an AI step |
| **Headless** | HTML | Load the page in a browser and run its JavaScript first. Set to **Screenshot (PNG)** for an image, or leave empty to fetch without a browser, which is faster |
| **Location** | – | Country or city to send the request from, for example `United States`. [Read more](https://help.decodo.com/docs/web-scraping-api-localisation.md) |
| **Device type** | – | Desktop or Mobile |

> [!NOTE]
>
> **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:

| Field | Description |
| - | - |
| `requested` | Number of URLs in the list |
| `scraped` | Number of pages returned |
| `failed` | Number of URLs that failed or were left out |
| `results` | One entry per page, with the same fields as **Fetch URL** |
| `errors` | One entry per failed URL, with `url` and `message` |

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.

## Run Search

Choose the **Search Type** first. The other fields depend on it:

| Field | Search SERP | Search E-Commerce |
| - | - | - |
| **Search query** | Required | Required |
| **Return parsed results** | On | On |
| **Return markdown** | Off, only shown when parsed results are off | Off, only shown when parsed results are off |
| **Headless** | Optional | Optional |
| **Location** | Optional | Optional |
| **Locale** | Optional, interface language such as `en-GB` | – |
| **Domain** | – | Optional, regional Amazon site such as `co.uk`. Defaults to `com` |

**Search SERP** calls the [**Google Search**](https://help.decodo.com/docs/web-scraping-api-google-search.md) target, and **Search E-Commerce** calls [**Amazon Search**](https://help.decodo.com/docs/web-scraping-api-amazon-search.md). 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)**.

> [!TIP]
>
> 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**](https://docs.zapier.com/platform/build/troubleshoot-action-timeouts). 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.

***

## Related

* [**n8n**](https://help.decodo.com/docs/n8n.md) – Build scraping workflows in n8n's visual automation platform.
* [**MCP Server**](https://help.decodo.com/docs/mcp.md) – Connect AI agents and MCP-compatible tools to Decodo.
* [**Web Data API playground**](https://dashboard.decodo.com/web-data/playground) – Test targets and settings before building a Zap.

***

> **[Support](https://direct.lc.chat/12092754)**
>
> 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](mailto:support@decodo.com).

> **[Feedback](mailto:feedback@decodo.com)**
>
> Can't find what you're looking for? Request an article! \
> Have feedback? Share your thoughts on how we can improve.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.