> For the complete documentation index, see [llms.txt](https://docs.scraperapi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scraperapi.com/integrations/automation-and-workflow-integrations/zapier-integration.md).
# Zapier Integration
Our official [ScraperAPI Zapier app](https://zapier.com/apps/scraperapi/integrations) lets you bring ScraperAPI into your Zapier automations. It enables you to:
* Extract data from any URL.
* Pull structured data from supported sites.
* Run Crawler jobs as steps in a Zap.
We handle the heavy lifting in the background: **proxy/user-agent rotation**, **CAPTCHA and bot-blocker bypass**, and **JavaScript rendering** (when necessary) so you can focus on building reliable data workflows without writing code.
{% hint style="info" %}
The ScraperAPI Zapier app is currently in **Beta** (v1.0.0) and listed under the **AI Web Scraping** category in the Zapier App Directory.
{% endhint %}
#### Installation
**1. Grab your ScraperAPI API key**
* Sign up for a ScraperAPI account at the [ScraperAPI Dashboard](https://dashboard.scraperapi.com/signup).
* Once logged in, navigate to your dashboard.
* Copy your API key from the dashboard.
**2. Connect ScraperAPI inside Zapier**
* Log into [Zapier](https://zapier.com) and create a new Zap (or open an existing one).
* Add a step and search for **ScraperAPI** in the app list.
* Select a ScraperAPI **action event** (e.g. *Extract Data From URL*).
* When prompted to **Connect** an account, paste your ScraperAPI API key and continue.
* Zapier validates the key and saves the connection (you only need to do this once). The connection is then reusable across all your Zaps.
#### How it Works
A typical scraping Zap looks like this:
1. A **trigger** step from another app starts the Zap (*Schedule by Zapier, Google Sheets, Webhook by Zapier, etc.*).
2. Add a ScraperAPI action step and pick the event you want (*Extract Data From URL, Get Structured Data* or a *Crawler* action).
3. **Map** input fields - type a value directly or insert a field from a previous step
4. Configure any optional parameters (*JS Rendering, Geo-targering, output format, etc.*)
5. Add one or more **downstream actions** to send ScraperAPI's output wherever you need it (*Google Sheets, Slack, a database, send an email, etc.*).
6. **Test** each step then turn the:zap:*Zap* :zap:on.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.scraperapi.com/integrations/automation-and-workflow-integrations/zapier-integration.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
