Google Sheets "Add a Row" reports success (with row number) but no data is written to the sheet

Questions
1

:bullseye: What is your goal?

Get data from online quiz into Google Docs spreadsheet

:thinking: What is the problem & what have you tried?

Hi Make Support,

I’m experiencing a consistent issue where the Google Sheets “Add a Row” module reports a successful execution — including a specific row number in the output — but the data is never actually written to the spreadsheet. I’ve reproduced this across two different spreadsheets and two different OAuth connections, so I believe this points to a server-side issue rather than a configuration mistake on my end.

Scenario

  • Scenario name: B2B Team Assessment
  • Module: Google Sheets > Add a Row (module #3)
  • Connection: “My Google connection” — tested with both an existing connection and a freshly created one, same result

What I expected

After running the module (via live webhook trigger and via manual “Run this module”), a new row should appear in the target sheet.

What actually happens

The module returns a successful output, e.g.:

OUTPUT
Bundle 1:
  Spreadsheet ID: 1aVRksKE-iN8oUfHpvJ62FwX7ZDgHmJHXJNsrqYFfSfA
  Table Range: 'B2B Quiz'!A1:O1
  Updates:
    Sheet: B2B Quiz
    Row Number: 2

No error is shown anywhere in the execution log (Initialization, Operation 1, Commit Phase, Finalization all show green checkmarks).

However, when I check the spreadsheet — both via the normal Google Sheets UI (hard refresh, Ctrl+End to jump to last used cell) and via a raw export bypassing any UI caching (https://docs.google.com/spreadsheets/d/xxxtq?tqx=out:csv) — row 2 does not contain the data Make claims to have written. Only the header row and a manually-typed test row are present.

Steps already ruled out

  1. Wrong spreadsheet/folder path — confirmed exact Spreadsheet ID match between Make’s module output and the browser URL of the sheet I’m checking.
  2. Wrong sheet/tab name — confirmed “Sheet Name” in Make matches the actual tab name exactly.
  3. Account/permission mismatch — confirmed the Google account connected in Make is the sole owner with Editor rights on the spreadsheet (checked via Share dialog).
  4. Stale OAuth token — created a brand new Google connection from scratch, re-authorized all requested scopes, reselected the spreadsheet via the ID Finder picker. Same result.
  5. Browser caching — confirmed via raw CSV export (gviz/tq endpoint) that the row is genuinely absent at the Google Sheets API level, not just a UI refresh issue.
  6. Reproduced on a brand-new spreadsheet (“B2B Quiz”) created specifically to rule out any legacy file corruption — same issue occurs.

Spreadsheet details for reference

  • Spreadsheet ID: [ID-name]
  • Sheet/tab name: B2B Quiz
  • Search Method used in module: “Select from all” (fromAll)

Question

Could you check on your end whether the Google Sheets API call for this module execution actually reaches Google’s servers, and what response is received? I’d like to understand whether this is an issue with the API call itself, a permissions/scope issue invisible from the Make UI, or something else on your platform side.

Happy to provide the scenario export, execution IDs, or any other diagnostic data you need.

Thanks,
Erwin

:clipboard: Error messages or input/output bundles

Bundle Validation Error

:camera_with_flash: Screenshots (scenario flow, module settings, errors)

Schermafbeelding 2026-06-19 235836.png
Schermafbeelding 2026-06-19 235836.png832×1372 85.5 KB

3

Hey there,

This isn’t a make support channel, it’s just random people here.

Can you show a screenshot of the module configuration and the output?

The screenshot you are showing is from something else, saying a row number was not provided.

4

Hello,

Adding to Stoyan’s answer, which is fundamental here as without data asked we can only guess.

First of all.
Let’s clarify which module you are using. Add a Row mentioned in the title adds new row on your sheet, in the first available row.
But you added screenshot of Update a row module which requires passing rowNumber parameter (id of row you want to update) which in your case is missing.

You mentioned that you:

But your output clearly shows row 2 was the one updated: So no jumping should be necessary.

This

Confirms that only 1st row was filled before adding new row.

What I’d check next: right-click the Add Row module and run it on its own.
Or better – duplicate module and feed it hardcoded values like “test”, “test”, “test” to rule out a value-formatting issue.

Have a nice day,
Michal