Form Replies to a Sheet: Make

What you build: An automation that drops every new form response into a Google Sheet as a fresh row, instantly.

Who it is for: Anyone collecting sign-ups, orders, or feedback through a form.

Time to build: About 15 minutes. No code, no AI.

The skill it teaches: Field mapping, the most-used skill in all of automation.

Want a working AI workflow in your inbox each morning? Join the free daily Beginners in AI newsletter.

Second stop in the no-code foundations of our AI Automation for Beginners (the hub). A form fills up a spreadsheet on its own, with each answer landing in the right column.

This sounds basic, and it is, but it teaches the single skill you will use more than any other: mapping, the act of telling app B which piece of data from app A goes where. Master this and most automations become obvious.

What does this automation do?

It watches a form for new responses. Each time someone submits, it adds one row to a Google Sheet, with their answers split neatly into the columns you choose.

A few real cases, none of them the usual ones:

  • A workshop host sends every sign-up into a “Registrations” sheet the team can sort and filter.
  • A landlord collects maintenance requests into a sheet, oldest first.
  • A café gathers feedback into one tab so they can spot patterns by week.

A spreadsheet is still the friendliest database in the world. This keeps it filled without copy-paste.

Why not just let the form fill its own sheet?

Some form tools can write to a sheet directly, but the moment you want the data in two places, or filtered, or sent onward, you need a real automation in the middle. Building it in Make from day one means you control where the data goes, not the form vendor.

And it keeps the door open. Once the row exists in a sheet, anything can read it: a notifier, a CRM, or later an AI step that scores it. The sheet becomes the hub, and you own the hub.

What do you need before you start?

  • A free Make account.
  • An online form (Google Forms works out of the box; Typeform, Jotform, and others connect too).
  • A Google Sheet with column headers already typed in the first row.

The key word is mapping. When you map, you click a field in the second module and pick which value from the first module fills it. It looks like dragging puzzle pieces into slots, and that is exactly what it is.

How does the workflow work, step by step?

Two modules. The form watches for responses; the sheet adds a row. The whole skill is in the connection between them:

ModuleAppWhat it does
Watch ResponsesGoogle FormsFires when someone submits the form
Add a RowGoogle SheetsWrites the answers into your sheet as a new row
Make scenario showing a Google Forms Watch Responses module connected to a Google Sheets Add a Row module
The finished scenario: a form response in, a spreadsheet row out.

Step 1: Watch the form for responses

Start a new scenario, add Google Forms, and choose Watch Responses. Connect your account and pick the form.

Run the trigger once so Make learns the shape of your questions. It needs one real submission to map against, so submit a test answer yourself first.

Step 2: Add a row to the sheet

Add a Google Sheets module and choose Add a Row. Pick your spreadsheet and the tab.

Now the main event: for each column in your sheet, click the field and choose the matching answer from the form step. Name to Name, Email to Email, and so on. This is mapping, and it is the whole job.

Step 3: Add a timestamp (optional but smart)

Add one more column called “Received” and map a Make formula into it so every row is dated:

{{formatDate(now; "YYYY-MM-DD HH:mm")}}

Now you can always sort by when a response arrived, even if the form does not send its own timestamp.

How do you run it and check the result?

Click Run once, then submit the form for real. A new row should appear in your sheet within seconds, answers in the right columns.

If a value lands in the wrong column, you mapped two fields the same way. Re-open the sheet module and fix the pairing. Once it is right, switch the scenario on.

What does this cost to run?

PieceFree tierIf you outgrow it
Make1,000 operations a month free$9/mo Core for heavy form volume
Google Forms + SheetsFree with any Google accountIncluded; no paid tier needed
AINot used hereAdd a scoring or tagging step later for pennies per row

Each response is one operation. A free Make plan handles roughly 1,000 submissions a month at no cost.

What can go wrong, and how do you avoid it?

  • Mapping the wrong field. The most common slip. Map slowly and run once to check before going live.
  • Missing headers. Type your column headers into row 1 of the sheet before you build, or Make has nothing to map to.
  • Renaming form questions later. If you edit the form, re-check the mapping; a renamed question can break the link.

Build against a test sheet first. Point it at the real one only once the columns line up.

Where does AI plug in later?

The moment a row exists, AI can read it. Add a step that scores each new lead, or one that reads open-text feedback and tags the theme. Those are our guides to qualify leads with AI and analyze survey answers with AI.

The pattern, as everywhere in the AI Automation for Beginners (the hub), is the same: collect the data with no-AI plumbing, then add one smart step that reads what you collected. The sheet you filled today is the input AI works from.

How do you build this in Zapier or n8n instead?

Form-to-sheet is the most universal automation there is. Every tool does it:

JobMakeZapiern8n
Watch the formGoogle Forms / Typeform moduleForm triggerWebhook or form node
Add the rowGoogle Sheets: Add a RowGoogle Sheets actionGoogle Sheets node
Stamp the timeformatDate formulaFormatter stepDate node

All three can do it. We teach Make because the visual canvas is the easiest place to learn. The same shape works in any of them, and Zapier vs Make vs n8n compares the three for beginners.

Want the ready-made template?

The steps above build it from scratch. If you would rather skip the setup, the importable Make blueprint is yours free: subscribe to the daily newsletter and the download is waiting on the thank-you page, next to our Special Reports. Import it, connect your own accounts, and you are running in minutes.

Subscribe free and grab the template →

Ready to add AI to this?

Book a 1-on-1 Live Claude AI Crash Course and we add a smart step to one of your automations together, screen to screen.

Book the 1-on-1 ($75) →

Want better prompts for later?

When you add a scoring step, the Library has prompts that return a clean label or number you can drop into a column.

Get the Prompt Library ($39) →

A new automation you can copy, every day

Free daily newsletter. Built for people who want to use AI well, not chase every model.

Free forever. Unsubscribe anytime.

Common questions

Does this work with Typeform or Jotform?

Yes. Swap the first module for your form’s app; the Add a Row step stays the same.

What if my form has more questions than sheet columns?

Map only the ones you want. You do not have to use every field.

Can it update an existing row instead of adding one?

Yes, with the “Update a Row” module and a lookup, but start with Add a Row; it is simpler.

Do I need to code anything?

No. The only typed thing is the optional date formula, and you can copy it from Step 3.

Will old responses get imported?

No. It only catches responses submitted after you turn it on.

Sources and official documentation

Last reviewed: May 2026. App fields change now and then; the official docs above are the source of truth.

You may also like

Want a head start? Book a 2-hour live AI crash course

A private, beginner-friendly session across Claude, ChatGPT, Gemini, Grok, and the wider landscape. Walk away knowing which tools fit your work and how to use them.

Book the 2-hour crash course · $125 →

Discover more from Beginners in AI

Subscribe now to keep reading and get access to the full archive.

Continue reading