Google Forms Notification Settings: What You Get by Email (and What You Do Not)

A Google Forms notification tells you exactly one useful thing: someone clicked submit.

It does not tell you who they are, what they selected, or how urgent their request might be.

To see the actual data, you still have to drop what you are doing, open a new tab, and scroll through the form responses.

This creates unnecessary friction, especially when you are managing a high volume of submissions or relying on the form for time-sensitive requests.

This guide covers how to set up the native email alerts, exactly what those alerts leave out, and how to build a custom setup when a generic ping is no longer enough.

How do I enable email notifications for new Google Forms responses?

Turning on the default email alert takes only a few clicks, but it works on a per-user basis.

The notification is not a global setting that applies to every collaborator automatically.

If you want to receive an email when someone fills out your form, you must enable it from your own Google account.

Here is the exact path to turn these alerts on:

1. Open your form in the Google Forms editor.

2. Click the Responses tab at the top center of the screen.

3. Look for the three vertical dots (the More menu) in the top right corner of the Responses section.

4. Click Get email notifications for new responses.

5. Look for a small popup at the bottom left of your screen confirming that email notifications are enabled.

Once you click this, a small checkmark will appear next to that option in the menu.

From that moment on, the Google account you are currently logged into will receive an automated email every time a respondent clicks submit.

If you share editing access with a colleague, they will not receive these emails by default.

Your colleague must log in, open the form, and follow those exact same steps to subscribe their own email address to the notification list.

This per-user design prevents collaborators from being spammed with alerts they did not ask for, but it often causes confusion for teams who expect a single toggle to alert everyone.

If you are building a complex form from a description and handing it off to a client, remember to instruct them to turn this setting on themselves.

What details are actually included in the default Google Forms email alert?

The native Google Forms notification is built for simplicity and privacy, which means it is extremely brief.

When you receive the alert, you are looking at a system-generated receipt rather than a summary of the data.

Here is a breakdown of what the default email actually contains:

• The form title: The subject line will always read "New response for [Your Form Title]".

• The response count: The body of the email notes which number response this is (for example, "Response 14").

• A generic button: A blue View summary button that links directly to the Responses tab in the form editor.

• The timestamp: The date and time the submission was recorded by Google's servers.

Because the alert is so basic, it leaves out almost everything you actually need to make a fast decision.

Here is what you will not find in the default email:

• The respondent's name or email: Even if your form requires them to log in or provide their email address, Google does not print this in the notification.

• The actual answers: None of the text fields, multiple-choice selections, or checkboxes are visible in the email body.

• File attachments: If your form includes a file upload field, the email will not contain the file, nor will it include a direct link to the uploaded document.

• Custom branding: You cannot change the layout, add your company logo, or alter the wording of the notification email.

This limitation forces a constant context switch.

When an email arrives, you experience the cognitive load of pausing your current task, clicking the button, waiting for the form editor to load, and navigating to the individual response just to see if the submission requires immediate attention.

For a low-traffic feedback survey, this is fine.

For an IT ticketing system or a client onboarding workflow, this lack of detail creates a severe bottleneck.

Why are my Google Forms email notifications not working?

Even when you flip the toggle, you might find that submissions are rolling in while your inbox remains completely quiet.

Because the notification system relies on the intersection of Google Drive permissions and your email provider's filtering rules, a single mismatch will break the alert chain.

Use this table to diagnose and fix a silent notification setup:

In practice, the multiple-account mix-up is the culprit behind nine out of ten missing notifications.

Browsers frequently default to the primary account logged into the session, meaning you might build the form on your work account but accidentally subscribe to alerts using your personal profile.

How do I send a custom confirmation email to the respondent?

Sending an email to yourself is only half the process.

Often, you need to send a confirmation receipt to the person who filled out the form.

Google Forms handles this natively through a feature called Response Receipts.

To set up an automated confirmation email for your respondents, you must first configure the form to collect their email addresses.

1. Open your form and click the Settings tab at the top.

2. Expand the Responses section.

3. Under Collect email addresses, select Responder input. This forces the user to type their email into a dedicated field at the top of the form.

4. Once email collection is active, a new setting will appear directly below it: Send responders a copy of their response.

5. Change this toggle from Off to either When requested or Always.

If you choose When requested, the respondent will see a small toggle at the bottom of the form right before they submit, asking if they want a receipt.

If you choose Always, Google sends the receipt automatically without asking.

The native receipt includes a full breakdown of the questions and the exact answers the respondent provided.

However, the introductory text of that email is pulled directly from your form's Confirmation Message.

You can edit this message in the settings.

1. Stay in the Settings tab.

2. Expand the Presentation section.

3. Look for Confirmation message and click Edit.

4. Type your custom message and click Save.

This message appears on the screen immediately after they click submit, and it is also injected into the top of the automated email receipt.

Because this message serves dual purposes, you need to write it clearly.

• ❌ Weak: Your response has been recorded.

• ✅ Strong: Thanks for submitting your IT request. Our team reviews tickets at 10 AM and 2 PM daily. A copy of your details is included below for your records.

Why it works: The strong version sets an exact expectation for the next step and references the email receipt directly.

Expert tip: If you are migrating paper-based processes into digital workflows, relying on native receipts is a good first step. But when handling complex intake forms, you often need to route entirely different confirmation emails based on what the user selected. For that, you will have to move beyond native settings and use Apps Script.

How can you build custom email alerts using Google Apps Script?

When the native notifications fail to meet your needs - usually because you want the actual form data in the email body, or you want to route alerts to different departments based on a specific answer - you have to write a script.

Google Apps Script is a JavaScript-based platform built directly into Google Workspace.

It allows you to listen for a form submission, extract the exact answers the user provided, format those answers into a readable email, and send it to any address you choose.

To access the script environment, open your form, click the three vertical dots in the top right corner, and select Script editor.

This opens a new tab where you can write custom code.

A standard notification script relies on three main components to function correctly:

• The Event Object: When a form is submitted, Google generates an event object (often labeled e in the code) that contains all the data from that specific submission.

• The Mail Service: You use the built-in MailApp.sendEmail() or GmailApp.sendEmail() methods to construct the outgoing message.

• The Trigger: Code does not run on its own. You must tell Google to execute your script specifically when a new submission occurs.

The logic flow inside the script editor is straightforward.

First, you define a function that accepts the event object.

Second, you pull the specific answers out of that object using methods like e.response.getItemResponses().

Third, you assign those answers to variables.

Finally, you construct an HTML email body and pass those variables in, so the final email reads like a customized summary.

Once the code is written, you must authorize it.

The first time you attempt to run or trigger the script, Google will present a stern warning screen stating that the app is unverified.

You must click Advanced, then click Go to [Your Script Name] (unsafe), and explicitly grant the script permission to send emails on your behalf.

The last step is setting up the trigger.

1. In the Apps Script editor, look at the left-hand sidebar.

2. Click the clock icon, labeled Triggers.

3. Click the blue Add Trigger button in the bottom right.

4. Select your function name, set the event source to From form, and set the event type to On form submit.

5. Click Save.

From that point forward, every time a user submits the form, Google's servers will silently execute your code, package the data, and fire off your custom email.

This method requires a basic understanding of JavaScript, but it completely removes the limitations of the default alerts.

You can write custom subject lines (e.g., "Urgent: Server Outage Reported by John"), include specific answers in the body, and send the email to ten different people at once.

Which notification method is best for your specific workflow?

Choosing how to handle notifications comes down to a trade-off between setup time and data visibility.

If you over-engineer a simple lunch order form with custom scripts, you waste time.

If you rely on native alerts for critical client onboarding, you waste time logging in to check the data.

Use this decision matrix to match the method to your actual workflow:

In practice, the version I see work best for mid-sized teams is skipping the Form notifications entirely and relying on a linked Google Sheet.

When you link a form to a Sheet, you can use the Sheet's built-in notification rules to send an alert right away or as a daily digest.

More importantly, you can use Apps Script on the Sheet side, which is often easier to write because you can reference simple cell columns instead of complex form response arrays.

FAQ

Can I send Google Forms notifications to multiple email addresses?

Using the native settings, you cannot send a single notification to a list of emails automatically. Each person who wants an alert must log into their own Google account, open the form as a collaborator, and manually turn on the notification toggle. If you need to broadcast a single submission to a team inbox or a mailing list without requiring them to log in, you must use Google Apps Script or a third-party add-on.

Do Google Forms email notifications include file upload attachments?

No, the default email notification does not include attached files or links to the files. It only alerts you that a submission occurred. To view the uploaded files, you must click the link in the email, open the form's Responses tab, and click the file link to view it in your Google Drive.

How do I turn off email notifications for a specific Google Form?

To stop receiving alerts, open the specific form in the editor and navigate to the Responses tab. Click the three vertical dots in the top right corner of that section. If notifications are currently on, you will see a checkmark next to Get email notifications for new responses; click that line once to remove the checkmark and disable the alerts.

Is there a limit to how many email notifications Google Forms can send per day?

Yes, native receipts and Apps Script emails are bound by your Google Workspace daily email quotas. For free consumer Gmail accounts, Apps Script can typically send 100 emails per day. For paid Google Workspace accounts, that limit increases to 1,500 emails per day, though native form receipts may be handled slightly differently by Google's internal routing.

Getting the right data to the right inbox turns a static form into a functional workflow. While the native Google Forms alerts are frustratingly sparse, leaning into Google Sheets notifications or spending an hour setting up a basic Apps Script bridges the gap. If you are tired of manually managing form creation and routing altogether, a tool like Doc2Form can generate the form straight from your existing documents, leaving you more time to focus on what happens after the user clicks submit.