Google Forms already has a built-in option to save every response in a linked Google Sheet. Use that if you need a raw response log. The Make design in this guide adds work only when you need a separate, validated Curated Leads table. It describes a repeatable configuration and synthetic test fixture; it is not a claim that Toolnavira has run this scenario inside a live Make account.
First decide whether you need Make at all
Open Google Forms, go to Responses and choose a spreadsheet destination if all you want is a table of submitted responses. Google's linked response spreadsheet captures submissions without a third-party automation. Check access permissions separately for the form and spreadsheet, because collaborator rights can differ. Source: support.google.com ↗ .
Add Make only for a concrete job the native link does not already solve: filtering malformed responses, normalizing fields, enriching data with permitted information, or building a separate list for a defined operational workflow. Do not sell more automation than the business needs.
Create a safe input and output contract
Use a test form under an account you control. Define the fields response_id, submitted_at, name, email, company and request_type; capture the actual Forms response identifier rather than inventing a permanent ID from an email address. In a separate spreadsheet or dedicated destination tab called Curated Leads, define columns response_id, submitted_at, name, email, company, request_type and source. Do not select the raw response tab that Google Forms writes automatically.
Keep the test free of customers, phone numbers and other private information. Synthetic addresses at example.com are enough to check processing rules. Agree on a timezone for submitted_at and a clear policy for blank optional fields. Use the same columns in the comparison against Zapier so the test remains meaningful.
Watch incoming responses with a documented module
Make documents Google Forms modules for watching and retrieving responses, and offers a template that watches responses and adds Sheets entries. In an authorized test account, inspect the currently available Watch Responses trigger, select the correct form and connection, and record its configured start position and schedule. These account-specific UI settings have not been independently checked for this tutorial. Sources: apps.make.com ↗ and www.make.com ↗ .
A scheduled watch may check for new records even when no new lead arrives. Document the checking interval and how it affects operations before making a cost estimate. Do not activate a live schedule or purchase extra credits merely to demonstrate the guide.
Validate fields before writing a lead
Map actual Forms field identifiers into the destination contract. Trim avoidable whitespace, standardize a comparable email representation and reject a missing email or a clearly malformed address under the test rule. This is only a syntax screen; it cannot prove a mailbox exists or that a person consented to follow-up communication.
Distinguish rejected leads from skipped duplicates. A rejected event should have an observable reason in a safe test log; it must not look like a successful append. Avoid placing private raw form values into public screenshots or error reports.
Search by response ID, then append conditionally
Look for the exact response_id in Curated Leads. When the ID is found, record a duplicate and do not append another row. When the search completed successfully and returned no match, append the mapped, validated row. When the lookup failed, stop the current item and investigate; a query error is not the same as a legitimate empty result.
A Make module may output zero bundles on an empty result. Inspect the actual zero-match behavior and route settings in the connected account before publishing screenshots or claiming a reliable branch. Google Sheets has no atomic uniqueness protection on the simple lookup-and-append flow. Simultaneous executions can still produce a duplicate. Source: apps.make.com ↗ .
Prevent accidental spreadsheet formula interpretation
Treat text fields as untrusted spreadsheet cell values. For example, a name or comment that begins with an equals sign should not unexpectedly execute as a formula in the destination sheet. Verify the current Sheets module's value-input options and chosen spreadsheet locale in a test file. Do not claim a particular option is available, safe or automatically escaped without testing that exact module.
Keep the raw response sheet intact and append only to the curated destination. Review headers and field mapping before enabling a scenario; a renamed or moved column can silently put data into the wrong place unless you catch it in the acceptance test.
Run the ten-event acceptance test on synthetic data
Prepare six unique valid responses R001?R006, then deliver R002 twice more, plus R007 with an invalid email and R008 without an email. The designed final state is six curated rows keyed by R001?R006, two duplicate deliveries skipped and two invalid events rejected. This is a local fixture outcome, not observed execution inside Make. Review both row IDs and cell values; a green module indicator alone is not sufficient.
Record test timestamp, plan, app-module versions, relevant mappings, screenshots with identifiers removed, run IDs, output rows and actual credit usage. Until those receipts exist, present any diagram or screen sequence as an illustrative setup. Do not generate fabricated run logs or screenshots.
Recover safely from timeouts and permission changes
Denied Sheets access must stop an append and surface an error; do not silently mark the lead processed. For temporary rate limits or connection loss, verify whether the action already created a row before retrying. If an append happened but a response was lost, blind replay can duplicate the record. Make describes incomplete executions and automatic retries for specific error types; configured handlers determine what actually happens. Source: help.make.com ↗ .
Document a manual fallback and a bounded retry procedure. A simple search-then-append approach is not exactly-once delivery, and this tutorial does not promise zero lost leads or universal recovery. Enable the live schedule only after an owner has reviewed permissions and the results of a genuine test.
Estimate usage and decide whether the workflow is worth it
Make counts module operations and expresses consumption in credits. Watch checks, one operation for each processed bundle in relevant modules, retries and exceptional features can all affect cost. Check the real run history and current plan instead of assuming six accepted rows equal six credits. Sources: help.make.com ↗ and help.make.com ↗ .
Stop here if the native Google Forms linked Sheet meets the actual business requirement. If the curated workflow is needed, the next validation is a bounded live test with the synthetic fixture and a verified permissions scope, followed by a review of errors, usage and maintenance effort. Evidence status on October 22, 2026: documentation confirmed, local acceptance fixture designed, no connected Make execution performed, and no affiliate recommendation or paid automation subscription activated.
Practical checklist
- Try native Forms-to-Sheets linking before adding Make
- Separate raw responses from a Curated Leads destination
- Map stable IDs, dates and required fields with synthetic data
- Reject malformed inputs and skip duplicate response IDs
- Test zero-match lookup and potential formula-like text safely
- Verify row values, failure handling, retries and actual credits
- Get owner approval before activating any real automation
Examples illustrate a process. They are not proof of hands-on testing or current pricing for any named software.