Google Sheets "Watch New Rows" not triggering in Make: 6 causes and fixes

By Oz Shamo · Updated 2026-09-29 · Get guides by email · YouTube · Telegram

Make's Google Sheets "Watch New Rows" runs but finds nothing? Six causes — polling, blank rows, starting row, Limit, renamed tab, connection — each fixed.

Disclosure: links marked "paid link" pay us a commission from the vendor if you sign up. Your price is unchanged, and every file here works without them. How we choose tools →

You add a row to the sheet, you wait, and the scenario does nothing. The run history shows the trigger ran and returned zero bundles — or nothing ran at all. This is the most-asked Google Sheets question on Make's community, and almost every thread ends with one of six causes. This page walks through them in the order that finds the problem fastest, with the exact menu names in Make's editor as of 29 September 2026.

One idea explains most of it: Watch New Rows does not "see" a row being added. On each run it asks Google for the rows below the last row it processed, treats anything it finds as new, and remembers the new position. Every cause below is a way that model breaks.

First, know which module you have

If your module has a clock icon on it, it is Watch New Rows and the rest of this page applies. If it has a lightning bolt, it is Watch Changes, and it will never fire for a new row: that is by design, not a bug.

Cause 1: it is a polling trigger, and the scenario is not scheduled

A polling trigger runs only when the scenario runs. Two things have to be true: the scenario's Scheduling toggle (bottom-left of the editor) is ON, and the interval has passed. On Make's Free plan the shortest interval is 15 minutes; on Core it is 1 minute (make.com/en/pricing, checked 29 September 2026). A row added at 10:01 to a scenario that checks every 15 minutes is found at about 10:15, not at 10:01.

1. Open the scenario. Bottom-left: is the Scheduling toggle ON? If it says OFF, nothing runs on its own — only "Run once" does.
2. Click the clock on the trigger module. Check "Run scenario" is "At regular intervals" and the minutes are what you expect.
3. Add a row, then click "Run once". If the row appears in the trigger's output bubble now, the module works and you were only waiting on the schedule.

Each scheduled check uses one operation whether or not it finds a row (Make Help Center, Operations). At every 15 minutes that is 96 checks a day, about 2,880 a month — almost three times the Free plan's 1,000 credits. If the sheet is filled by a form, a booking tool or another app, the better design is to skip the sheet as trigger altogether: send the data to a Make webhook and let that scenario write the row. The two blueprints below do exactly that.

Cause 2: a blank row — or a row that only looks filled

Make's documentation is blunt: "If a sheet contains a blank row, Make doesn't process all subsequent rows." The module reads down from the last processed row and stops at the first empty one. A spacer row, a row someone cleared instead of deleting, or a row at the top left empty "for later" all end the table as far as Make is concerned.

The opposite problem is just as common and harder to spot. If a column has a formula copied down a thousand rows, or an ARRAYFORMULA, those rows are not empty: they contain a formula result (often an empty string). Make processed them on the first run, remembers row 1,000 as the last one, and your new typed row at row 12 is "old". The same happens with a template whose data-validation or formatting was applied to the whole column — formatting alone is fine, but pre-filled formulas are not.

1. In the sheet, press Ctrl+End (Cmd+End on a Mac). If the cursor lands far below your data, something fills those rows. Select them and delete the rows (right-click → "Delete rows"), not just their contents.
2. Look for any row inside the data that is empty. Delete it (the row, not the cells).
3. Move formula columns out of the table Make watches, or compute them in Make instead. If the formula must stay in the sheet, put it in a separate tab that references the data tab.
4. Then reset the starting point (Cause 3), because Make still remembers the old position.

Cause 3: the starting point is wrong (deleted test rows, "Choose where to start")

The trigger remembers a position. If you added five test rows, ran the scenario, deleted them and typed a real lead into row 2, Make believes rows 2–6 were already processed and waits for row 7. This is the thread that comes back every month on the community ("Watch New Rows does not track new rows after removing a row", July 2025).

1. Right-click the Watch New Rows module.
2. Click "Choose where to start". (The same window opens on its own when you first configure a polling trigger; if you closed it, this is where it lives.)
3. Pick "All" to process every existing row and then watch for new ones, or "From now on" to ignore what is there. "Choose manually" lets you pick a specific row as the last processed one.
4. Click "Run once". The bubble above the module shows how many rows it returned.

Do this every time you delete rows from the watched sheet. If you clear test data often, keep a "status" column instead and use Search Rows with a filter "status is empty" plus Update a Row at the end that writes the time — the pattern Make's community moderators recommend for the same reason.

Cause 4: the Limit field

Limit is the maximum number of rows the module returns per run. The default is small. If ten rows arrive between two checks and Limit is 1, the scenario processes one row per run and the backlog drains at one every 15 minutes — which looks exactly like "not triggering" for the last nine. On the free plan, that is a backlog of two and a half hours.

• For testing, set Limit to 1 or 2 so a "Run once" is cheap and easy to read.
• For production, set Limit to the most rows you expect between two checks, with headroom. Every module after the trigger runs once per row, so 20 rows with 3 more modules is 61 operations in one run.
• A very high Limit with "All" as the starting point processes the whole sheet at once — fine on a 30-row sheet, expensive on a 5,000-row one.

Cause 5: a renamed or copied tab, or the wrong spreadsheet

The module stores the spreadsheet ID and the sheet (tab) name. Rename the tab from "Sheet1" to "Leads" and the module keeps asking for "Sheet1" — Make returns an error like "Requested entity was not found" or the run simply returns nothing, depending on the mode. Making a copy of the spreadsheet for a new client and pointing the form at the copy is the same problem: the scenario still watches the original.

1. Open the module. Check the "Spreadsheet ID" matches the long string in the sheet's URL between /d/ and /edit (a copy has a different one).
2. Re-select the "Sheet Name" from the dropdown rather than trusting the stored value.
3. If "Table contains headers" is Yes, check "Row with headers" — for headers in row 1 across six columns it should read A1:F1. Headers in row 3 with the range left at row 1 make Make treat your titles as the first data row and shift everything by one.
4. Click OK and "Run once".

Cause 6: the connection is the wrong Google account

A connection is a Google account. If the connection in the module belongs to your account and the sheet lives in a client's Drive that never shared it with you, the module cannot read it and reports a 403 or 404 in the run history — nothing arrives, and the scenario looks dead. The same happens when the client removes your access, or when someone re-authorises the connection while logged into the wrong Google account.

1. Click the module → the "Connection" field. Note the email address in the connection name.
2. Open the sheet in a browser logged in as that email. If it asks for access, that is the problem: share the sheet with that account (Editor), or create a connection for the account that owns it.
3. In Make, left menu → "Connections" → find the connection → "Verify". A red "Not verified" means re-authorise.

Duplicate runs: the opposite problem

If every row produces two messages, one of two things is running twice. Either a clone of the scenario (from testing, or from importing the blueprint a second time) is also switched on — check Scenarios for two with similar names — or a Search Rows scenario has no status update, so tomorrow it finds the same rows again. Each Watch New Rows module keeps its own position, so two active copies both process every row.

How to test properly with "Run once"

1. Set Limit to 1. Right-click the trigger → "Choose where to start" → "From now on".
2. Add one row at the bottom of the data, directly under the last filled row.
3. Click "Run once". The trigger's bubble should show 1. Click it to read the output — the column names should match your headers.
4. Check every later module's bubble shows 1 too. Fix any that show an error, then run again with a second row.
5. Set Limit back to a production value and turn Scheduling ON.

Still broken? Check these three things

• The run history. Left menu → the scenario → "History". Open the last run. If the trigger shows 0 operations, the scenario never ran (scheduling). If it shows 1 operation and an empty output, it looked and found nothing (position, blank row, formulas). If it shows a red error, read it: 403/404 is the connection or the sheet, 429 is Google's quota.
• A brand-new tab. Create a new sheet tab with one header row and one data row, point a fresh Watch New Rows module at it with "All", and Run once. If this works and your real tab does not, the real tab has hidden fillers or blanks. Compare row counts with Ctrl+End.
• Whether you need this trigger at all. If a form, a booking tool or another system creates the rows, it can call a Make webhook directly: instant, one operation per real event, and none of the position problems above. The guide on Make with Google Sheets below covers the pattern.

Make + Google Sheets: the modules, the limits and the pitfallsWhich module to use for each job, what each costs in credits, and the six mistakes that break a sheet quietly

If you are starting a new Make account for this, the free plan is enough to build and test everything on this page: Sign up (one month of Core free) → paid link · we earn a commissionPaid link. If you sign up through it we earn a commission from Make; your price is the same, and the link gives you one month of Core free.

1. Make Apps Documentation — Google Sheets modules (Watch New Rows fields; "If a sheet contains a blank row, Make doesn't process all subsequent rows"; Watch Changes limits)
2. Make Help Center — Set up the trigger ("Choose where to start", right-click on the module)
3. Make Help Center — Operations (one operation per trigger check)
4. Make — Pricing (Free: 1,000 credits, 2 active scenarios, 15-minute interval; Core: 1 minute)
5. Make Community — "Watch New Rows does not track new rows after removing a row" (July 2025)
6. Make Community — "Google Sheets Watch New Rows won't detect new row" (July 2025; blank rows, polling)
7. Make Community — "Watch New Rows on Google Sheet module seems to have an issue" (March 2025; polling vs instant)
8. Make Community — "Watch new rows not taking the next row" (June 2024; status-column pattern)

Next step

All automations →

DUPLICATE CHECK

Returning lead → recognised → "second contact", not "new lead"

A returning lead is greeted as new. Before logging, the phone is checked against the log; if it is there, the alert says "came back", not "new lead".

MakeGoogle SheetsTelegramTally4 ops/run✓ imported in Make

MISSING INFO

Form arrives incomplete → an email asking for exactly what is missing

A lead without a phone, an order without an address. Instead of someone chasing, one email lists the missing fields; the lead is logged as "incomplete".

MakeGoogle SheetsGmailTally3 ops/run✓ imported in Make

SOURCE REPORT

Every Sunday: leads by source → one message with the change from last week

Which source brings the leads? Every Sunday one Telegram message lists this week's leads per source (website, Facebook, referral) beside last week's.

MakeGoogle SheetsTelegram5 ops/run✓ imported in Make

Get one new Make automation each week

Get the full 21-blueprint pack (ZIP) by email, then one new automation a week. Everything on the site stays free to download without it.

Leave this empty

Email addressSubscribe

Yes — email me BuilderStack's weekly issue: one new Make automation or guide a week, from O.S. Maintenance Buildings Ltd (Israel). It may include paid links. Unsubscribe anytime.

Optional. We use your address only to send this email; it is stored by Brevo (EU) until you unsubscribe. You can access or delete it at any time — see the privacy policy. Privacy policy.

What will it cost? Make cost calculator →Build your automation plan →