The built in notification in Google Forms is easy to find and easy to outgrow. Open a form, click Responses, open the More menu, and there is an option labelled "Get email notifications for new responses". It works. It sends an alert to whoever switched it on, telling them that a response arrived.
What it does not do is send anything to the person who filled in the form, include the answers in the message, route different submissions to different people, or let anyone other than the subscriber know that the alert went out. Every one of those gaps is why the Google Workspace Marketplace has a crowded shelf of notification add-ons, and why the search for one usually starts after a process has already broken.
What the built in setting covers, and what it does not
The native option is an alert to editors, not a reply to respondents. The other native mechanism is Link to Sheets, which appends each response as a row in a spreadsheet. Between them these two cover the case where one person watches a form and reads the rows.
They stop covering it as soon as any of the following is true. The respondent needs a confirmation with a copy of what they submitted. Different answers need to reach different teams. More than one colleague needs to know that something arrived and that someone has taken it. The message needs to come from an address that is not the personal account of whoever set the form up.
Each of those is a separate reason to install something, and they are worth separating, because the add-ons on offer solve quite different subsets of them.
The three shapes of notification add-on
Search the Marketplace for form notifications and the results fall into three groups.
The first is Google's own add-on, listed as Form Notifications, published by Google and free of charge. Its listing describes exactly two behaviours: messages delivered to form respondents as they submit, and messages delivered to form owners and editors on predetermined response thresholds. As of the listing updated on 10 June 2026 it shows more than 42 million installs and a 4.1 rating. The threshold behaviour is the distinctive part. It is built for "tell me when 100 people have signed up", not for "tell me about each one".
The second group is the full featured third party notification add-ons. Email Notifications for Google Forms, published by Digital Inspiration, is the largest of them, with more than 21 million installs and a 4.0 rating on a listing updated 20 May 2026. These add conditional routing, multiple notification rules per form, CC and BCC, file attachments from Drive, and delivery to channels other than email.
The third group is single channel bridges. DiscordNotify, TelegramQ and similar add-ons do one thing: push the submission into a chat platform. They are small, cheap and appropriate when the only requirement is visibility in a channel the team already watches.
| What is needed | Built in setting | Google's Form Notifications | Full featured third party add-on |
|---|---|---|---|
| Alert an editor that a response arrived | Yes | Yes, at thresholds | Yes |
| Confirmation email to the respondent | No | Yes | Yes |
| Include the submitted answers in the message | No | Limited | Yes |
| Different recipients based on the answers | No | No | Yes, on paid tiers |
| Post to Slack, Teams, Discord or a webhook | No | No | Yes, usually on the top tier |
| Cost | Free | Free | Free tier with caps, then paid |
Note that Google publishes a warning alongside every Marketplace listing: it does not verify reviews or ratings. Install counts are the more reliable signal, and even those say nothing about whether an add-on is maintained.
The permission being granted is larger than it looks
Every notification add-on has the same architectural problem to solve. Google Forms has no mail server of its own, so anything that sends email has to borrow an account. That account is yours.
Google's own add-on states the permissions plainly on its listing. It asks to view and manage the forms it is installed in, to run when the user is not present, to send email as the user, and to see the primary Google Account email address. Third party add-ons ask for the same shape of access, because there is no other way to do the job.
Three consequences follow, and they are the ones that matter when choosing.
The message comes from the installer's address. If the person who set up the form leaves the organisation and their account is suspended, the notifications stop. This is the single most common way an automated acknowledgement silently dies.
The sending counts against that account's quota. Google publishes the Apps Script limits: 100 email recipients per day for consumer accounts such as gmail.com, and 1,500 per day for Google Workspace accounts. Trigger runtime is capped as well, at 90 minutes a day for consumer accounts and 6 hours a day for Workspace. A registration form that gets busy will hit the 100 recipient ceiling on a personal account in an afternoon, and the failure is silent from the respondent's side.
The add-on's own tier sits underneath the Google quota, and is usually stricter. Email Notifications for Google Forms publishes its limits directly: the free edition sends 20 emails per day and allows a single notification rule per form, the Standard edition raises that to 400 recipients per day and up to five rules per form, and the Enterprise edition reaches 1,500 recipients per day and requires a Google Workspace account. The same documentation notes that the daily sending limit is shared across every form under the same Google account, so a busy form will consume the allowance of a quiet one.
What the paid tiers actually unlock
For that add-on, the free tier covers notifying the respondent and nothing much else. Removing the "Sent via" footer, adding CC and BCC recipients, sending from a different alias, and sending conditional notifications based on the answers all require the Standard edition. Attaching Drive files, sending SMS, posting to Google Chat or Discord, sending webhooks, and manually resending a notification to an old response all require the Enterprise edition.
The last of those is worth calling out. Being able to resend to a response that already arrived is the feature people look for after something has gone wrong, which is exactly when discovering it is on the top tier is least welcome.
Writing the trigger yourself instead of installing one
An add-on is not the only route. A form submit trigger in Apps Script, attached to the form or its linked spreadsheet, can read the submitted answers and send whatever message is wanted, with full control over the wording, the recipients and the conditions.
This is the right answer more often than it gets credit for, particularly where the routing rules are unusual or where an administrator has locked down Marketplace installs. It costs an hour to write and it has no licence fee.
It inherits every constraint described above, though, and adds one. The script runs as whoever authorised it, sends against that account's quota, and stops when that account does. The extra constraint is maintenance. A script written by one person and documented nowhere becomes a liability the moment that person moves on, and the symptom of a broken script is the same as the symptom of an exhausted quota, which is silence. If the script route is taken, it is worth adding a failure notification so that a broken trigger announces itself rather than being discovered by an applicant.
Deliverability, and the address on the envelope
The other question that surfaces once messages are going to people outside the organisation is whether those messages arrive at all. Mail sent through a personal Gmail account is generally delivered, but it arrives from an individual rather than from the organisation, which looks wrong on a confirmation for a public programme.
Sending from an organisational domain is the fix, and it is a paid feature almost everywhere. Some add-ons offer sending from a different alias on a mid tier and a generic no-reply address on the top tier, with the no-reply option requiring a Google Workspace account. Dedicated form tools generally handle the domain question themselves and record whether each message was opened, which is a different proposition from sending and hoping. Whichever route is chosen, check what the recipient sees in the From field before the first public form goes out.
Where an add-on stops being the answer
Notification add-ons solve delivery. They do not solve the queue, and it is worth being clear about where the line is.
An add-on can tell four people that an application arrived. It cannot record that the second of those four picked it up. It can send a templated confirmation. It cannot show the next person who opens the response what was sent, because the message lives in the sender's mailbox and the spreadsheet row has no idea it happened. It can route by answer. It cannot hold a status that a human sets after reading.
The tell is simple. If the notifications are working perfectly and the team is still asking each other "did anyone reply to this one", the missing piece is not notification. It is ownership and state, and no add-on to a form builder supplies it, because the form builder has nowhere to put it.
At that point the choice is between building the missing layer, usually a spreadsheet with Owner and Status columns plus a convention nobody enforces, or moving to a tool where the reply, the owner and the status live on the response itself. The features to look for are an assignable owner, stages a person sets, and a send box on the same screen as the answers, with every message kept on the record.
Choosing one without regret
Four checks, in order.
Start by writing down the recipient list and what each recipient needs. Respondent confirmation, team alert and conditional routing are three different requirements, and the cheapest add-on that covers all three is often not the most popular one.
Second, check which account will send. Installing on a shared or role account rather than an individual's, where the organisation's rules allow it, removes the failure that happens when someone leaves.
Third, compare the add-on's daily limit against the busiest realistic day, not the average, and remember the limit is usually shared across all forms on that account.
Fourth, check that a Workspace administrator has not restricted Marketplace installs, because in many organisations they have, and discovering that after choosing is a wasted afternoon. Where installs are restricted, the alternatives are an administrator approved allowlist entry or a form tool that sends mail itself. The pricing pages of dedicated form tools are worth a look at this point, because per seat pricing with sending included often lands close to a paid add-on licence plus the Workspace seat it requires.
What to change first
Write down the exact list of who should 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 anyone other than the subscriber needing to see that a reply went out, the gap is ownership rather than notification, and a tool like Halict that keeps the reply on the response is the thing to compare against the add-on.
Q1. Can Google Forms email the person who filled in the form without an add-on?
No. The built in setting under Responses notifies editors who have subscribed, not respondents. Sending a confirmation to the person who submitted requires either Google's free Form Notifications add-on, a third party add-on, or an Apps Script trigger written by hand.
Q2. Why did the notification emails suddenly stop arriving?
The usual causes are the daily sending quota and the sending account. Add-ons send through the Google account that installed them, and Google's published Apps Script quota is 100 email recipients a day for consumer accounts and 1,500 a day for Google Workspace accounts. Add-on tiers impose their own lower caps on top. If the account that installed the add-on was suspended or had its password changed, sending stops entirely.
Q3. Is the free tier of a notification add-on enough?
For a low volume form with one notification rule and no conditional routing, often yes. Email Notifications for Google Forms, for example, allows 20 emails per day and a single rule per form on its free edition. Conditional routing by answer, CC and BCC, and sending from a different alias sit on paid tiers across most of these add-ons.
Q4. What permissions does a Google Forms notification add-on need?
Access to the forms it is installed in, permission to run when the user is not present, and permission to send email as the user. Google's own Form Notifications listing states these explicitly. There is no way to avoid the mail permission, because Google Forms has no sending capability of its own and the add-on has to borrow an account.
Q5. Can an add-on track which submissions have been handled?
No. Notification add-ons deliver messages. They do not record an owner, a status or the content of a reply, and the sent message lives in the sender's mailbox rather than on the response. Teams that need that generally move the queue into a tool that stores the reply alongside the answers, or maintain it by hand in a spreadsheet.