# Connect Google Sheets to Zapier & Make Zapier and Make both read JSON over HTTP, so any Google Sheet you expose as a REST API becomes a data source for your automations — filtered and paginated, without a dedicated Sheets integration. *Last updated: 2026-07-11 · Source: * ## Key facts - Zapier and Make both read **plain JSON over HTTP** — a *Webhooks by Zapier → GET* step or Make's *HTTP → Make a request* module — so any JSON endpoint is a data source, no dedicated Sheets integration needed. - The Google Sheets API allows **300 read requests per minute per project** and **60 per minute per user**. Past that it returns `429 RESOURCE_EXHAUSTED`. ([source](https://developers.google.com/workspace/sheets/api/limits)) - A cached endpoint reads the sheet **once per TTL**, not once per request — so 10,000 visitors become one upstream read, and Google's quota stops being your problem. - PasteSheet's MCP server exposes three tools — `list_tabs`, `get_schema` and `query_rows` — and is **read-only by design**: an agent can query your sheet but can never modify it. ## Read a sheet from Zapier or Make 1. Paste your sheet URL into PasteSheet to get a JSON endpoint like `https://pastesheet.com/api/your-endpoint-id`. 2. In Zapier, add a **Webhooks by Zapier → GET** step (or in Make, an **HTTP → Make a request** module). 3. Set the URL to your endpoint, adding query params to filter: `?status=active&sort=created&order=desc`. 4. Map the returned `data` array into the next step — each row is a typed JSON object keyed by your columns. ## Why go through an API The native Google Sheets steps in these tools are row-trigger oriented and tied to your Google account. A REST API instead gives you an on-demand, queryable read of the whole sheet — with filtering, sorting, and pagination as plain URL params — and it is edge-cached, so busy automations do not hammer Google or trip [rate limits](https://pastesheet.com/guides/google-sheets-api-rate-limits). It is read-only, so an automation can consume the data but never corrupt the sheet. To build a whole app this way, see [building a no-code app on Google Sheets](https://pastesheet.com/guides/google-sheets-no-code-app). ## Frequently asked questions ### How do I connect Google Sheets to Zapier without the native app? Expose the sheet as a REST API with PasteSheet, then use a Webhooks by Zapier GET step pointed at the endpoint URL. Zapier reads the JSON rows directly, with filtering via query parameters. ### Does this work with Make (Integromat)? Yes. Use Make's HTTP module to GET the endpoint URL. The response is JSON you can map into any downstream module, filtered and sorted with URL parameters. ### Can the automation write back to the sheet? No. PasteSheet is read-only, so automations consume sheet data safely but cannot modify it. Edit the sheet directly for changes. ## Sources - [Usage limits — Google Sheets API](https://developers.google.com/workspace/sheets/api/limits) — Google ## Related guides - [Build a No-Code App on Google Sheets](https://pastesheet.com/guides/google-sheets-no-code-app) — Build a no-code app backed by Google Sheets: turn a sheet into a REST API and MCP server, then wire it to your front end, no-code tools, or an AI agent. - [Turn Google Sheets Into a REST API (No Code)](https://pastesheet.com/guides/google-sheets-rest-api) — Turn a public or restricted Google Sheet into a live JSON REST API with filtering, sorting, and pagination — no backend, no code. - [Google Sheets API Rate Limits (60/min)](https://pastesheet.com/guides/google-sheets-api-rate-limits) — Google Sheets API rate limits are 300 reads per minute per project and 60 per user. Here is why read-heavy apps hit a 429 — and how caching removes the wall. --- [PasteSheet](https://pastesheet.com) turns any Google Sheet into a live REST API and MCP server for AI agents — no backend, no code. Canonical HTML version of this page: