Make.com Google Sheets Search Rows returns nothing? What actually happens

说明与用途

在 Make.com 场景中，Google Sheets Search Rows 模块在未找到匹配行时返回空包，但后续模块仍会执行，导致错误。通过检查电子表格设置、标题、范围和过滤值，清理数据并在空包上进行路由，可正确处理已找到和未找到的行。

问题

When Make.com's Google Sheets Search Rows module finds no matching rows, it outputs an empty bundle and the next module still runs, causing errors or unintended behavior.

结果

The scenario now correctly identifies when no rows match, prevents downstream errors, and can branch to add new rows or skip processing as needed.

工作流

• Check spreadsheet ID, sheet name, file type, and connection.
• Verify "Table contains headers" and column range settings.
• Run Search Rows without a filter and limit=5 to inspect actual cell values.
• Add filter conditions one by one to identify mismatches.
• Clean data: trim spaces, enforce case‑insensitive operators, convert text to numbers, format dates as YYYY‑MM‑DD or use parseDate().
• Adjust limit and sort order if needed.
• Handle not‑found cases by routing on Total number of bundles or Row number existence.
• Avoid using Array aggregator for not‑found handling.
• Use data store for duplicate checks if appropriate.

证据

When Search Rows finds no matching rows, there's no error, and the route doesn't stop either. The module outputs one empty bundle: no row data, no Row number, and Total number of bundles = 0.

来源

Remove the filter, run the module once with a small limit, and compare what Make receives with your filter.

来源

The most common mismatch is invisible: Unpaid (with a space) isn't Unpaid. Capitalisation matters too.

来源