An email notifications add-on for Google Forms is worth installing when one of four things is needed: a confirmation sent to the person who filled in the form, the submitted answers inside the email, different recipients depending on the answers, or a message posted to a chat tool. Google Forms itself does none of those. Its built in setting sends one alert, to the editor who switched it on, saying that a response arrived. If that single alert is enough, nothing needs installing.
If it is not enough, the choice comes down to three things the add-on listings rarely put side by side: which account the mail is sent from, how many messages that account may send per day, and which features sit on the paid tier. This guide lays those out using figures read from Google's documentation, the Google Workspace Marketplace, and the add-on publishers' own pricing pages on October 8, 2026.
What Google Forms sends without any add-on
The built in option lives here: open the form, click Responses, click More (the three dots), then Get email notifications for new responses. Google's help page for this setting adds a tip pointing to its own Form Notifications add-on for anything more.
What the built in alert does:
- Emails the editor who turned it on, once per response.
- Works per person. Each editor who wants alerts has to switch it on for themselves.
What it does not do:
- Email the respondent.
- Include the answers in a way anyone can act on without opening the form.
- Send to an address that is not an editor of the form.
- Route by answer, or post anywhere other than an inbox.
The other native tool is linking the form to a spreadsheet, which appends each response as a row. Between the alert and the sheet, one person can watch one form comfortably. The add-on search usually starts when a second person or a respondent needs to be told something.
One change from Google is worth knowing while planning. The same help page now states that starting in September 2026, Forms has new limits of 1 GB total storage and 500,000 responses per form. Busy, long running intake forms should be checked against that figure.
The add-ons people actually install
A Marketplace search for form notifications on October 8, 2026 returned these at the top. Install counts and ratings are as displayed on the listing. Google states on the search page that it does not verify reviews or ratings, so install counts are the steadier signal.
| Add-on | Publisher | Installs | Rating | What it is built for |
|---|---|---|---|---|
| Form Notifications | 42M+ | 4.1 | Confirmation to respondents, alerts to editors at response thresholds | |
| Email Notifications for Google Forms | Digital Inspiration | 21M+ | 4.0 | Confirmations, routing by answer, webhooks, SMS, Slack, Discord, Google Chat |
| Advanced Form Notifications | Jackie (Guokai) Han | 1M+ | 4.1 | Notifications to respondents and owner, closing the form |
| Form Notify | Form Notify | 861K+ | 4.6 | Notifications plus mail merge from Sheets, conditional sending |
Google's own Form Notifications is free of charge. Its listing (updated June 10, 2026) describes exactly two behaviours: messages to respondents as they submit, and messages to owners and editors on predetermined response thresholds. That second part matters. It is designed for "tell me when 50 people have registered", not "tell me about each registration with the answers attached". Teams that want a per submission alert with content usually end up with a third party add-on.
Smaller single purpose add-ons also exist that only push submissions into one chat tool. They are reasonable when the whole requirement is visibility in a channel the team already reads.
Every add-on sends as you
Google Forms has no mail server of its own. Any add-on that emails someone has to borrow a Google account, and that account belongs to whoever installed it.
Google's Form Notifications listing shows the permissions it asks for on its Permissions tab:
- View and manage forms that this application has been installed in
- Allow this application to run when you are not present
- Send email as you
- See your primary Google Account email address
- See your personal info, including any personal info you've made publicly available
Third party add-ons ask for the same core access, because there is no other way to do the job. Three practical consequences follow.
The From line shows the installer. A confirmation for a public programme arrives from an individual's address unless the add-on supports sending from an alias.
The sending stops when that person's account does. If the installer leaves and the account is suspended, the trigger stops firing. Nothing tells the respondents. This is the most common way an automatic confirmation dies quietly.
The quota is that account's quota. Google publishes the Apps Script limits that all of these add-ons run under:
| Limit | Consumer account (gmail.com) | Google Workspace account |
|---|---|---|
| Email recipients per day | 100 | 1,500 |
| Email recipients per day within the domain | 100 | 2,000 |
| Total trigger runtime per day | 90 minutes | 6 hours |
Source: Google Apps Script quotas page, checked October 8, 2026.
A registration form promoted from a personal Gmail account can pass 100 recipients on its first busy morning. After that, confirmations simply do not go out until the next day.
What the free tier stops short of
Add-on publishers set their own caps beneath Google's. Digital Inspiration publishes a full comparison for Email Notifications for Google Forms, and it is a useful map of where the market draws the line between free and paid.
| Feature | Free | Standard | Enterprise |
|---|---|---|---|
| Daily sending | 20 emails | Up to 400 recipients | Up to 1,500 recipients (needs Google Workspace) |
| Notification rules per form | 1 | Up to 5 | Unlimited |
| Notify the respondent | Yes | Yes | Yes |
| CC and BCC | No | Yes | Yes |
| Send from a different alias | No | Yes | Yes |
| Conditional emails based on answers | No | Yes | Yes |
| "Sent via" footer removed | No | Yes | Yes |
| Resend to old responses | No | No | Yes |
| Attach files from Google Drive | No | No | Yes |
| SMS, Google Chat, Discord, webhooks, push | No | No | Yes |
| Generic no-reply sender | No | No | Yes (needs Google Workspace) |
Source: Digital Inspiration's Form Notifications pricing page, checked October 8, 2026.
Two notes on the same page change how the numbers read. The licence applies per Google account, upgrading every form owned by that account. And the daily sending limit is shared across all forms on the account: if the limit is 1,500 and one form has already used 200, every other form on that account has 1,300 left for the day.
The row most teams discover late is resend to old responses. It is the feature people look for after a confirmation failed to go out, which is exactly when finding it on the top tier is least welcome. Check for it before choosing a tier.
Writing the trigger instead
An add-on is not the only route. Google's developer documentation includes a tutorial for sending emails about new Google Forms submissions with Apps Script. An installable form submit trigger reads the answers and sends whatever message is needed, with full control over wording, recipients, and conditions, and no licence fee.
It is the better answer in two situations: routing rules that no add-on menu expresses cleanly, and organisations where an administrator has restricted Marketplace installs.
The trade-offs are the same as for add-ons, plus one more:
- It runs as the person who authorised it and stops when their account does.
- It sends against that person's daily quota from the table above.
- Nobody else may know it exists. When the author changes roles, a broken script looks exactly like an exhausted quota: silence.
If this route is chosen, add a failure notification to the trigger settings so a broken run emails someone, and keep the script in a shared drive with a one paragraph note on what it does.
Where notifications stop helping
Notification add-ons solve delivery. They do not solve the queue.
An add-on can email four colleagues that an application arrived. It cannot record that the second colleague picked it up. It can send a templated confirmation. It cannot show the next person who opens the response what was sent, because the email lives in the sender's mailbox and the spreadsheet row has no record of it. It can route by answer. It cannot hold a status that a person sets after reading.
The sign is easy to spot. If notifications are arriving reliably and the team still asks each other "did anyone reply to this one", the missing piece is not another alert. It is an owner and a status on each response, plus a record of the reply. Google Forms has nowhere to put those, so no add-on for it can supply them.
At that point there are two options. One is a spreadsheet with Owner and Status columns and an agreement that everyone keeps them current. The other is a form tool where each response carries an owner, a stage, and its own email history, so the reply is sent from the same screen as the answers and stays on record. For teams whose forms feed admissions, recruitment, or enquiry handling, the typical setups look much the same.
A checklist before installing
- Write down every recipient and what each one needs. Respondent confirmation, team alert, and routing by answer are three separate requirements. The free tier of most add-ons covers only the first.
- Decide which account will send. Where policy allows, install on a shared role account rather than an individual's, so a departure does not stop the mail.
- Compare the busiest realistic day with the daily limit. Use the lower of Google's quota and the add-on tier, and remember the add-on limit is shared across every form on the account.
- Check the From line. Send a test submission and look at what the respondent sees. An alias or a no-reply sender is a paid feature on most add-ons.
- Ask the Workspace administrator first. Many organisations restrict Marketplace installs, and approval takes longer than setup.
When the sum of a paid add-on licence and the Workspace seat it requires is on the table, it is also worth comparing per seat pricing on form tools that send mail themselves.
What to change first
List who must receive what, then check it against the daily sending limit of the account that would send it. If the list includes routing by answer or more than one person needing to see that a reply went out, the gap is ownership rather than notification, and a tool such as Halict that keeps the reply on the response is the comparison to make before buying an add-on licence.
Q1. Can Google Forms email the respondent without an add-on?
No. The built in setting under Responses, More, Get email notifications for new responses only alerts the editor who switched it on. A confirmation to the respondent needs Google's free Form Notifications add-on, a third party add-on, or an Apps Script trigger.
Q2. Why did Google Forms notification emails stop arriving?
The usual causes are the daily quota and the sending account. Add-ons send through the account that installed them, and Google's Apps Script limit is 100 recipients a day on a consumer account and 1,500 on a Google Workspace account, with the add-on's own tier often lower. If the installing account was suspended, sending stops completely.
Q3. Is Google's own Form Notifications add-on enough?
It is free and covers confirmations to respondents and alerts to editors at predetermined response thresholds. It is not designed for a detailed alert on every submission or for routing by answer, which is where third party add-ons come in.
Q4. Does a notification add-on need permission to send email as the user?
Yes. Google Forms cannot send mail itself, so the add-on sends through the installing account. Google's Form Notifications listing names the permission directly as Send email as you, along with running when the user is not present.
Q5. Can a notification add-on track which responses have been answered?
No. These add-ons deliver messages but do not record an owner, a status, or the text of a reply on the response. Teams that need that keep extra columns in a spreadsheet or use a form tool that stores replies with each response.
Q6. Is there a limit on how many responses a Google Form can collect?
Google's help page states that starting in September 2026, Forms has limits of 1 GB total storage and 500,000 responses per form. Forms expected to collect continuously for years should be planned around that figure.