Your website has an inquiry form, and people are filling it out. Someone still has to find each request, add it to your team’s list, and respond. This guide takes you from a Google Forms submission to a spreadsheet where each inquiry has a person responsible and a next step.
Chill&AutomateUpdated September 27, 2026
untangle → move on
✓
When this guide helps
Use this guide if any of these situations sound familiar:
You receive form notifications by email and manually copy the details into another spreadsheet.
A customer says they submitted the form, but their request is missing from your project list.
A transfer runs again and creates two copies of the same inquiry.
Start with the direct Google Forms–Sheets connection. Then separate the original submissions from your team’s working list and learn how to recognize a repeated transfer. The first version needs no additional automation service.
The approach
Choose a form that keeps submitted answers even if sending them to your spreadsheet fails. Copy the contact, request, and a link to the original answer into your shared sheet. Save the unique submission number too: if a transfer runs twice, this number tells you the message is already there. A genuinely different job from the same customer still needs its own row.
Check off steps as you finish them. Progress stays in this browser; reset it below when you start again.
Two tabs, one register
Use a Requests tab for one row per job: ID, summary, contact, owner, status and next date. A Sources tab records each submission: system, response ID, received time, original reference and linked request ID. Do not overwrite the original whenever a transfer runs again.
Keep submissions with missing required information in a needs-information queue. Do not delete them or mark them ready for a reply. If two inputs look alike but have different IDs, compare their content; a customer email address is not a job identifier.
A simple Google Forms route
In Google Forms, open Responses and select a spreadsheet destination. Keep the response tab for incoming data and create your operating register alongside it. Check form and spreadsheet access separately. Unlinking a spreadsheet stops new transfers while leaving existing rows in place.
For manual processing, assign a stable source ID that does not change when rows are sorted. The Google Forms API exposes responseId, but a standard linked spreadsheet may not expose it as a column. Do not design automatic matching around a field absent from your input.
When the transfer fails
Reconcile original submissions against the Sources tab, rather than counting notification emails. Assign someone to each unlinked input. If the destination record may have been created before an error, look for it first. Create it again only after ruling out an existing result.
Automation also needs a concurrency rule. Looking up a record and then creating it are two separate operations. At low volume, start with one writer and an exception queue; concurrent writers need storage that can enforce a unique key.
Filled example
Fictional example to explain the process, not a real client record.
Worked example: submission FORM-101 creates website inquiry JOB-01. Replaying FORM-101 retrieves JOB-01. A new FORM-102 from the same contact asks for training, so it becomes JOB-02. FORM-103 lacks contact details and remains in needs-information with an owner and review date.
Source system and ID
Website form; submission FORM-101
Received time and original reference
September 28, 2026, 9:00 a.m.; original response retained as FORM-101
Request ID and short description
JOB-01; client requests designs for five website pages
Contact / missing input
Contact supplied in the original form; requested delivery date is missing
New / linked / needs information
New → recorded as JOB-01. A replay of FORM-101 links to the same row.
Owner, next action and due date
Coordinator Alex; ask for the delivery date; September 28 by 4:00 p.m.
Take the worksheet with you
An intake record and replay rules. Use them as a form specification or a manual processing sheet.
Expand the blank template below, select the text, and paste it into your document. Replace the brackets with your own information, using the filled example above for guidance. Keep a separate copy for each job. You can also download the text. No sign-up required.
For a simple inquiry form, start with Google Forms connected directly to Google Sheets. That transfer needs neither Make nor n8n. If inquiries already arrive in HubSpot, keep the form there and record each job separately.
Prices and terms checked September 27, 2026, in the currency shown by the vendor. Quotes may vary by country; confirm your currency, tax and commitment before buying. Example budgets exclude any additional tax.
Budget for this job
Forms → Sheets needs no paid connector. In Make, reading, searching and writing can all consume credits; one inquiry is not necessarily one credit. Start with manual intake at low volume and identify the repeated transfer.
Keep each original submission and its linked working row. If a transfer fails, you can see which request still needs handling.
What can go wrong
A customer may see a success message even if the details never reach your next spreadsheet. Check the original response and its entry in the working list.
✓
How to check it works
Submit sample details and find them in both places. Process the same response again: the team should still see one inquiry to handle.
Where to start today
Connect one form to one spreadsheet. Once the sample inquiry appears with a named handler, expand to other forms.