Build a working scenario: Google Sheets (Watch New Rows) → Filter (only continue if Email or Phone is filled in) → Slack (post new enquiry details to a channel). This is a practice/learning scenario, not yet live for a client.
What is the problem?
The Google Sheets “Watch New Rows” module keeps returning stale/incorrect output that doesn’t match the actual spreadsheet content.
My spreadsheet (“Intake test v2,” Sheet1) currently contains only Row 1 (headers: Name, Email, Message, Phone) and Row 2 (Name: Aisha Khan, Email: [email protected], Message: “Enquiry about a tenant…”, Phone: blank) — confirmed directly in Google Sheets.
Despite this, the module’s output consistently shows completely different data that doesn’t exist in this sheet at all: Name: Dylan, Email: [email protected], Message: “Hello this is a test,” Phone: “Hello this is a test.” This looks like leftover data from an earlier, different spreadsheet I used while testing.
What have you tried so far?
I’ve tried:
Deleting and re-adding the Google Sheets module entirely
Creating a brand new spreadsheet and explicitly selecting it (confirmed correct Spreadsheet ID and Sheet Name)
Resetting “Choose where to start” to “All” via right-click, then saving the whole scenario, then running again
Checking for blank rows (none present)
Running “Run this module only” and “Run once” multiple times
Hard-refreshing the browser and reopening the scenario fresh
This sounds like it may be trigger state rather than the sheet contents themselves.
One split I would make: does the stale “Dylan / [email protected]” row appear only in the module’s sample / choose-where-to-start output, or does it also appear in a brand-new execution after you add a fresh row while the scenario is watching?
If it is only the sample/start-point output, I would reset the trigger start point and force Make to watch the exact spreadsheet ID + sheet ID again, not just the visible spreadsheet name. If it appears in a new execution too, then I would suspect the scenario is still bound to an old spreadsheet/sheet behind the module configuration.
Thanks for the reply. It’s the second scenario not the first - this shows up in an actual live execution, not just the sample. Specifically, I add a new row to the sheet and run once on the full scenario and the message that comes through in Slack (real output not preview) still shows the old Dylan/[email protected] spreadsheet data instead of the new row. So basing off what you said, it looks like the scenario is still bound to old spreadsheet data behind module configuration, even though the visible spreadsheet name in the module settings shows the correct new data. Is there a way to check/force the underlying spreadsheet/ sheet id make is connected to is seperate from what’s displayed in the drop down?
2.- it will appear a list of already existing rows, here you should see current row with the current information as a preview (confirm that is the updated information)
Check the information if the information doesn’t correspond to the google sheets then this first module is misconfigured.
But
If the information is correct, then the error is not this module but probably your slack module is receiving wrong information. and I suggest to search other other modules.
There is, export the scenario as a blueprint and open the JSON. Find your Google Sheets module and look at the raw “spreadsheetId” and “sheetId” parameters directly. The dropdown labels can lag or cache stale data even when you’ve picked a new sheet, this is why it is best to compare the JSON ID with the new sheet’s URL which will confirm if they’re mismatched.
If they are mismatched just delete the entire field value. Then either re-add the module fresh or use “Search by ID” but paste the spreadsheet ID manually instead of picking from the list. If you still are not getting results it might just be better to try an entirely new Google Sheets connection, as sometimes Make can cache sheet metadata at the connection level.