You can build a Zapier pipeline for permitted public-web data, but there is no single “scrape any site” trigger. Start with the source’s official API or RSS feed; use an authorized webhook when the source can push updates; schedule a check when it cannot. For accessible public pages, Zapier’s documented beta Web Search and Web Reader actions are additional options—not a guarantee that every page is available or that collecting it is permitted.
Keep the workflow small and auditable: collect, filter, normalize, and send only the fields you need, while preserving the source URL and observation time where practical. Technical access does not establish permission under a site’s terms or the rules that apply to your use.
Choose the least brittle collection route
Before building a Zap, check what the source itself offers and whether you are authorized to collect and use the information. Prefer an official API or published RSS feed over reading page markup: these routes are generally less dependent on a site’s layout. If the source can send you events, an inbound webhook avoids repeatedly checking for changes. Use scheduled polling only when a feed, API, or push mechanism is unavailable and the source permits the approach.
| Route | Use it when | Important trade-off |
|---|---|---|
| Official API | The source documents an API and grants access appropriate to your use. | Use the API’s authentication, pagination, and usage rules; the Zapier documentation cited here does not specify limits for a particular third-party API. |
| RSS | The source publishes a feed of new items. | Zapier can trigger on one feed or multiple feeds, but this gives you feed entries rather than arbitrary page data. |
| Inbound webhook | An authorized source can push new or changed records to Zapier. | Configure the sender to use the correct Zap URL, HTTP method, and payload format. Large payloads have limits. |
| Scheduled check | You need to periodically query an authorized API or another permitted source. | This is polling, not an instant change notification. Choose an interval that is appropriate for the source and your use. |
| Web Search and Web Reader by Zapier | You need to discover public pages or read accessible public-page content. | Both are documented as beta. Search results can point to pages that block scraping; Reader respects robots.txt and errors when a page blocks scraping. |
Zapier’s RSS trigger offers “New Item in Feed” and “New Items in Multiple Feeds.” Its documentation recommends leaving the default “Different Guid/URL” setting in place for most cases. See Zapier’s RSS trigger guide.
#1 Best Overall
For public pages, Web Search by Zapier can return up to 20 public search results, including titles, URLs, and snippets. Web Reader by Zapier is intended to read public pages and can handle JavaScript-heavy pages. These beta actions can help with discovery and reading, but they do not make an inaccessible page accessible or authorize collection.
Plan a small, auditable Zap
A practical pipeline has distinct stages so you can see what entered the workflow, what was kept, and what was sent onward. The following is a design pattern assembled from documented Zapier components, not a tested, guaranteed recipe for a particular source or destination.
- Choose a trigger. Select an RSS trigger for a published feed, Catch Hook or Catch Raw Hook for an authorized sender, a schedule for periodic checks, or a documented Web Search/Web Reader action when appropriate.
- Collect only permitted data. For RSS, use the feed item. For a webhook, use the fields the sender supplies. For an API, follow its documented authentication and response format. For page reading, use Web Reader only where access is allowed.
- Filter early. Add a filter so irrelevant records do not continue to later steps. Use criteria that correspond to the fields actually returned, such as a category, status, or date.
- Normalize fields. Map source fields into a consistent shape for the destination—for example, title, source URL, observed time, and the specific values you need. Handle missing or differently formatted fields deliberately rather than assuming every item is identical.
- Send selected fields to the destination. Store only what the downstream task requires. When you need durable history or large records, consider storing the full record in a suitable data store and passing an identifier or selected fields through the Zap.
- Retain provenance. Where the source supplies it, keep the original URL and the time you observed the record. That makes later review and correction more practical.
For an inbound event, Zapier’s Catch Hook parses a request into fields; Catch Raw Hook exposes raw request data and headers. For outbound requests, Webhooks by Zapier supports GET, POST, PUT, and Custom Request actions. Zapier describes GET as retrieving information, POST and PUT as able to send files, and Custom Request as the option when you need more control over the method or request details. See the inbound webhook guide and the outbound webhook guide.
Configure webhooks and scheduled checks carefully
Inbound webhooks
Use the Catch Hook or Catch Raw Hook trigger URL supplied by the Zap, then configure the sending application to make the matching request. Zapier’s troubleshooting guidance says inbound webhook data should be sent as XML, JSON, or form-encoded data. It distinguishes POST requests, which use Catch Hook or Catch Raw Hook, from GET requests, which use Retrieve Poll.
Catch Hook is the more straightforward choice when you want Zapier to parse incoming fields. Choose Catch Raw Hook when you need raw request data or headers. Do not send sensitive information merely because a webhook URL is difficult to guess; treat the URL and any credentials as secrets.
Scheduled polling
A schedule can start a Zap at intervals so a later step checks an authorized feed or API. Zapier’s scheduling guide explains how to configure a workflow to run at selected intervals: Schedule Zap workflows to run at specific intervals. A schedule only starts the check; the downstream request still needs to handle the source’s authentication, response shape, pagination, and permitted request frequency.
Account for payload size and retention
Payload size can break a workflow even when its logic is sound. The figures below are stated in the relevant Zapier Help Center pages updated in 2026; check those pages again if you are designing around a limit.
| Component | Documented constraint | Practical implication |
|---|---|---|
| Webhook actions | 5 MB maximum, per Zapier Help Center page updated 2026-08-10. | Keep outbound request bodies within the documented maximum. |
| Inbound webhook triggers | 10 MB maximum; Catch Raw Hook has a 2 MB maximum, per page updated 2026-05-29. | Choose the trigger with its lower limit in mind; reduce or split oversized input where the sender and use case allow. |
| Create Item in Feed action | About 10 KB of data per action, per page updated 2026-05-29. | Do not treat this as a general-purpose archive for large records. |
| Zapier-created RSS feed | Keeps the 50 most recent items; entries clear after 14 days without new additions, per page updated 2026-05-29. | Do not rely on it as permanent history. |
Zapier’s RSS action documentation also says there are no actions to edit or remove items from the created feed. Read the RSS feed action guide before using a Zapier-created feed as part of a downstream process.
Respect access and use boundaries
Zapier documents Web Reader as respecting robots.txt; if a site blocks scraping, the action returns an error. That is a technical behavior, not a complete statement of legal permission. A page being publicly visible—or technically readable—does not by itself establish that you may collect, retain, or reuse its content. The rules may depend on the website’s applicable terms, the data involved, your jurisdiction, and what you plan to do with it. Use sources and methods you are authorized to use, review relevant terms, and seek authorization or legal advice when appropriate.
Keep the pipeline reliable and economical
- Prefer stable interfaces. A documented API, RSS feed, or source-generated webhook is less exposed to page redesign than a workflow built around page content.
- Keep records lean. Large payloads can exceed webhook limits. Store full records in a suitable system when durable history is needed, and pass an identifier or necessary fields through Zapier.
- Expect latency under load. Zapier says high webhook volumes may delay passing data to later steps. A received request is not necessarily processed immediately in a burst.
- Plan for retries and duplicates. Design the destination mapping so repeated delivery does not unintentionally create duplicate records when the source or workflow may resend an event. Use a stable source identifier where one is provided.
- Do not assume an undocumented rate allowance. Zapier says webhook action rate limits apply, but the cited help page does not state a numeric rate. Check current product guidance and avoid designing around a guessed threshold.
Troubleshoot by checking the handoff
The Zap does not trigger
- Confirm the sender is using the exact webhook URL shown by the intended Zap, not a URL from a different trigger.
- Match the method to the trigger: POST uses Catch Hook or Catch Raw Hook; GET uses Retrieve Poll, according to Zapier’s troubleshooting guide.
- Check that the sender sends XML, JSON, or form-encoded data in a supported format, and that the test request contains the fields you expect.
- Confirm the Zap is configured and enabled, and run a fresh test after correcting the sender. See Zapier’s webhook troubleshooting guide.
The trigger fires but later steps fail or arrive late
- Inspect the received sample and identify whether a field is absent, nested differently, or too large for the next action.
- Compare the payload against the limits for the exact component in use, particularly the lower Catch Raw Hook maximum.
- If the sender delivers bursts, allow for downstream delay and check each run’s step history instead of treating delay as proof that the event was lost.
Web Reader returns an error
Check whether the target is public and whether access is blocked by the site’s robots.txt or other controls. Zapier documents an error when scraping is blocked; do not try to evade a block. Choose an authorized API, feed, or contact the site owner if access is needed.
The RSS workflow misses older items
RSS triggers are based on feed entries and the feed’s available history, not a promise of complete historical extraction. Verify that the source feed contains the items you need and that your pipeline does not treat a Zapier-created feed’s 50-item, 14-day behavior as an archive.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Or skip the browser setup
If your immediate need is a rendered screenshot rather than structured page data, ScreenshotNeo is a separate website screenshot API and MCP server from Yorker Media—not a Zapier scraping trigger and not a substitute for an authorized API or feed. A single GET request returns an image or PDF. This example saves a WebP screenshot; documentation is at ScreenshotNeo’s API docs.
Free tools Windows power users keep installed
One-click scans. No signup required.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpScreenshotNeo accepts a consent banner like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing, with page-verdict and billing headers in each response. Its MCP server provides screenshot and PDF tools for AI agents. The free plan includes 1,000 shots per month without a card; paid plans start at $5 for 3,000 shots. A screenshot is visual output, not a structured extraction of page fields for a Zap.
Sign up for 1,000 free screenshots a month, with no card required.
Build for the source you are actually allowed to use
A dependable Zapier collection workflow starts with the source’s supported route, keeps only the data the downstream task needs, and makes payload, retention, and delay constraints visible. Use page-reading actions only when access is allowed; when the source’s terms or your intended use are unclear, resolve that before collecting.
Frequently Asked Questions
Can Zapier scrape any public website?
No. Its documented Web Reader action can error when a site blocks scraping, and the product documentation does not establish permission for any particular site or use.
Recommended Free Tools
Is Web Reader by Zapier generally available?
The cited Zapier Help Center page describes Web Reader as a beta feature; availability and behavior can change, so check the current page.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
