On this page
You run your work in Notion, and the answers arrive in Google Forms. So every new response means copying a name, an email and three answers into a database by hand. Getting Google Forms to Notion without that copy-paste is the goal of this guide.
Google's help page on where to save form responses names two places: "When responders fill out your form, you can find a summary of the responses in the form or you can store the responses in a linked Google Sheet." Notion isn't one of them, so you need a bridge. Below are the three bridges people use, what Google's, Notion's and Zapier's own pages say about them, and a fourth route: a form builder that writes each response into Notion itself.
Every fact about Google Forms, Notion and Zapier comes from their own pages, which we checked on November 2, 2026. At the end there's a free mapping worksheet that plans every question's Notion property before you connect anything.
Three ways to get Google Forms to Notion#
| Way | What you get in Notion | Where answers are kept |
|---|---|---|
| Embed the Google Form in a Notion page | The form itself, shown on the page | In Google Forms, or a linked Google Sheet |
| An automation tool such as Zapier | A new database item for each response | In Google Forms, plus a copy in Notion |
| A Google Forms add-on | Whatever the add-on's listing describes | Depends on the add-on |
Embed the Google Form in a Notion page#
This is the quickest of the three. Google's sharing help page says you can share a form "through email, social media, or embed on a website or blog". In the form, open the More menu, select Embed HTML and copy what shows.
Notion's embeds help page covers the other side: "Enrich your Notion pages with other apps, PDFs, forms, and interactive maps." Add an Embed block, then "In the menu that appears, paste the content's URL or embed link."
Here's the catch. The embed puts the form on your Notion page, but it's still a Google Form. The answers still go where Google's help page says: the form's Responses tab or a linked sheet. As a Google Forms to Notion route, an embed shows the form, and the answers stay with Google.
Connect Google Forms and Notion with Zapier#
An automation tool watches the form and writes to Notion for you. It's the no-code Google Forms to Notion route that fills a database. Zapier's Google Forms and Notion page lists a Google Forms trigger called New Form Response: "Triggers when a new form response is received." On the Notion side, it lists actions such as Create Data Source Item: "Creates an item in a data source."
So each response becomes a new item in your Notion database, and the answers stay in Google Forms too. The page also says "Free tier available"; check Zapier's own pricing page for what each tier includes before you build on it.
Use a Google Forms add-on#
Google's add-ons help page says: "You can use add-ons to do more with Google Docs, Sheets, Slides, and Forms." In a form, click More, then Add-ons, and pick one to install.
We don't name or test any add-on here. If you search the add-on store for Notion, read each listing, and read the access request before you click Allow. Google's page says "For most add-ons, a message will appear requesting access to data that the add-on needs to work."
Build it in HornetForms: responses straight into Notion#
The three bridges above all keep Google Forms in the middle. The fourth route skips the bridge: build the form in a form builder with a native Notion integration, so each response lands in your database with no extra tool.
HornetForms has one, and it works on every plan, Free included, with unlimited responses within fair use. Here's what it does:
- One Notion page per completed response. Each person who submits the form gets their own page in your database.
- Answers go to matching property types. Email, URL, phone, number, date, select and multi-select where the question fits, and text for the rest.
- A new database or one you already have. HornetForms can create the database for you, or write into an existing one.
- A Response ID property. HornetForms adds it, so a retried delivery never makes a duplicate page. Keep it in your database.
- Hidden fields arrive as text. Tag each link with a value like
source=newsletter, and Notion records where each response came from. - Files arrive as file names, with a Response link to the full response.
Respondents never need an account to answer, even to upload a file. That's worth knowing if you used file uploads in Google Forms: Google's question types page says "To answer this question, responders need to sign in to a Google Account."
The integrations page lists every tool HornetForms connects to. For the full setup, field by field, read our guide to Notion forms.
Plan the Notion database before you connect it#
Whichever Google Forms to Notion route you pick, plan the database first. Ten minutes of planning saves an afternoon of fixing. Notion's database properties page says properties "add all kinds of context to your database items, like due dates, task owners, relevant URLs, last edited timestamps, and more." Its steps are short: "To create your first property in a database, click Add property. Give your property a name, then choose a property type."
The trick is picking the right type for each question. Here's how each Google Forms question type carries over when you rebuild the form in HornetForms, and the Notion property type HornetForms picks for it. The Google type names come from Google's question types page.
| Google Forms type | Rebuild in HornetForms as | Notion property |
|---|---|---|
| Short answer | Short text (or Email, URL, Phone, Number) | Text (or Email, URL, Phone, Number) |
| Paragraph | Long text | Text |
| Multiple choice, Dropdown | Multiple choice, Dropdown | Select |
| Checkboxes | Checkboxes | Multi-select |
| Linear scale, Rating | Linear scale, Rating | Number where it fits, or Text |
| Date | Date | Date |
| Time | Time | Text |
| Multiple choice grid, Checkbox grid | Matrix | Text |
| File upload | File upload | Text (file names, plus a Response link) |
One row deserves a second look. A Google Forms short answer often holds an email or a phone number. Rebuild it as an Email or Phone question, and Notion gets an Email or Phone property instead of plain text. Need help picking? Here's which question type to pick for each kind of answer.
The Notion forms guide linked above covers the rest of the database design: naming properties to match your questions, and which columns your team keeps for itself.
Move the Google Form across#
You have two ways to bring the form itself over to HornetForms.
- Rebuild it. Open HornetForms' doc-style editor, type "/" for each question type and follow the table above. Our step-by-step guide on how to make a Google Form is a handy checklist of what your current form has: sections, theme, settings and the confirmation message.
- Import a copy with AI. If you have the form as a PDF or a Word (.docx) file, HornetForms' AI rebuilds it for you to review. Each file uses one AI generation and can be up to 10 MB. Free includes three AI generations a month. Most browsers can save a page as a PDF from the print menu.
If you're still deciding whether to switch, here's a fair comparison with Google Forms.
Check the logic after either route. Google's question types page says multiple choice, checkboxes and dropdowns can route people: "Based on a responder's answers, you can send them to a certain section of the form." In HornetForms, conditional logic covers show, hide, require, jump, calculate, hide submit and redirect on every plan. The logic, piping and calculations guide has more on how the rules fit together.
Bring your earlier answers along#
Your old Google Form answers can join the same database. Google's responses help page shows how: click Responses, then More, then Download responses (.csv).
Notion's import help page says you can add a CSV to an existing database with Merge with CSV and match its columns to your properties. It also warns: "CSV merges add rows. They don't update existing rows." So merge each file once, and check for duplicates before you do.
Keep Google Sheets in the loop too#
Notion is where the work happens, but some people still want a spreadsheet for monthly reports. HornetForms also connects to Google Sheets, Slack and Discord, on every plan.
A new Google Sheets spreadsheet from HornetForms starts with a "Response ID" column and a "Submitted at" column, then one column per question, then a "Response link" column.
If the form takes a payment, Notion, Sheets, Slack and Discord get the answers; the Payment block never becomes a field there. For the full list of destinations, see send form responses to Google Sheets, Slack or Notion.
Get the Google Form to Notion mapping worksheet#
The worksheet turns the table above into a plan for your own form. Download the mapping worksheet (Excel, .xlsx). It has four tabs:
- Start here: six steps, a color key and notes on what HornetForms sends to Notion.
- Mapping: room for 40 questions. Type each Google Form question, pick its Google Forms type from a list, and the sheet suggests the HornetForms question type and shows the Notion property type. An optional column lets you change the question type (for example, a short answer that holds an email) or give the property its own name. A Check column flags a missing question, a missing type or two rows with the same property name.
- Types: every Google Forms type from Google's help page, with the HornetForms question to use and the Notion property it gets.
- Summary: how many questions you listed, how many rows need a fix and how many properties of each Notion type you'll need.
The Mapping tab starts with an example workshop sign-up form in grey italics, so you can see it working. Delete those rows before you add your own.
Prefer a plain file? The type guide (CSV) has the Types tab on its own: Google Forms type, HornetForms question, Notion property type and a note for each. It opens in Google Sheets, Excel or Notion.
Google Forms to Notion questions, answered#
Can you link Google Forms to Notion?#
Yes, in three ways: embed the form in a Notion page, connect the two with an automation tool such as Zapier, or install a Google Forms add-on. An automation tool such as Zapier writes each response into a Notion database. For an add-on, its listing says what it does. An embed shows the form, while answers stay in Google Forms.
Is there a free way to send Google Form answers to Notion?#
An embed shows the form, but the answers stay with Google, so look at the other routes. Zapier's page says "Free tier available"; check its pricing page for what the free tier covers. HornetForms' Notion integration is on the Free plan, which is free forever with no card needed.
What about the answers I already collected in Google Forms?#
Download them from the form's Responses tab as a CSV, then use Notion's Merge with CSV to add them to your database. Notion's import page says merges add rows and don't update existing ones, so merge each file once.
The small print#
Google Forms, Google Sheets and Google Workspace are trademarks of Google LLC. Notion is a trademark of Notion Labs, Inc. Zapier is a trademark of Zapier Inc. HornetForms is not affiliated with, endorsed by or sponsored by any of them. Everything above about their products reflects their own help and app pages as of November 2, 2026: Google Docs Editors Help, the Notion Help Center and Zapier's Google Forms and Notion page. Check those pages on the day you set up your workflow.
Try it on your next form#
Pick the Google Form whose answers you copy into Notion most often, and retire that copy-paste job for good. Fill in the mapping worksheet, rebuild the form and connect your database. Sign up for free and send your first response straight to a Notion page.