scraperapi-zapierlisted

# ScraperAPI in Zapier — Zap Build Guide This skill helps you guide a user through building a **Zap** that uses the official **ScraperAPI** Zapier integration. Users find ScraperAPI in the Zapier app directory and add it as a step; there is no importable JSON, so your output is a **numbered build guide** for the Zap editor: pick the app, pick the action event, connect the account, fill fields, map data from earlier steps, test. Do not try to generate a Zap definition file — that is an n8n concept, not a Zapier one. Zaps are built in the browser. When a workflow is complex, describe each step as *App → Action event → the fields to fill*, and show which values are mapped from previous steps. ## The one thing to get right first: ScraperAPI is action-only The ScraperAPI integration exposes **actions only — no triggers**. A Zap cannot *start* with ScraperAPI. Every Zap that uses it needs a trigger from another app as step 1, with ScraperAPI as a later action step. This is the single most common point of confusion, so lead with it. Pick the trigger that matches the user's intent: | The user wants to… | Use this trigger (step 1) | |--------------------|---------------------------| | Scrape on a schedule (hourly/daily/weekly) | **Schedule by Zapier** | | Scrape on demand from an incoming request | **Webhooks by Zapier → Catch Hook** | | Scrape each row of a list | **Google Sheets / Airtable** (New/Updated Row) | | Scrape when something happens in another app | that app's native