How to Send Google Form Responses to Multiple Email Addresses

Collecting form responses is only half the job. Getting those responses to the right people -- your sales lead, your operations manager, your finance team -- is the other half. And this is exactly where Google Forms falls short.

Google Forms has a built-in email notification feature, but it sends notifications to exactly one person: the form owner. If you need multiple people to receive responses, you are left cobbling together workarounds. This guide covers five methods to send Google Form responses to multiple email addresses, from free built-in options to paid tools, with a clear comparison of what each method can and cannot do.

The Default: Google Forms Only Emails the Form Owner

Google Forms has a simple notification toggle buried in its settings. To enable it, open your form, click the Responses tab, then click the three-dot menu in the top right corner of the Responses section. Select "Get email notifications for new responses." That is it. Every new submission triggers an email to the Google account that owns the form.

There is no way to add additional email addresses from this settings panel. There is no CC field, no distribution list option, no forwarding rule. If you created the form from your personal Gmail account and you need your team to see the responses, Google Forms gives you nothing out of the box.

This limitation is why an entire ecosystem of add-ons, scripts, and third-party tools exists to solve what should be a basic feature.

Method 1: Add Collaborators (Free, but Manual)

The simplest workaround is to add collaborators to the form and have each one opt into notifications individually.

How to Set It Up

1. Open your Google Form in edit mode.
2. Click the three-dot menu in the top-right corner of the page and select "Add collaborators."
3. Enter the email addresses of everyone who should receive notifications. They need Google accounts.
4. Each collaborator receives a link to the form editor. They must open the form, go to the Responses tab, click the three-dot menu, and individually toggle on "Get email notifications for new responses."

Limitations

• Each person must opt in manually. You cannot enable notifications on their behalf. If someone forgets to toggle it on, they will not receive anything.
• Collaborators get editor access. There is no "notification only" permission level. Everyone you add can modify the form, delete responses, and change settings.
• No customization. Every collaborator receives the same notification email with the same content. You cannot filter which responses each person sees or customize the email template.
• No conditional routing. You cannot send billing-related submissions to finance and support-related submissions to engineering. Everyone gets everything.

This method works for small teams of two or three people who all need to see every response and who can be trusted with edit access. Beyond that, it breaks down quickly.

Method 2: Google Sheets Notification Rules (Free, but Delayed)

If your Google Form is connected to a Google Sheet -- which it should be for any form you care about -- you can use Sheets' built-in notification rules to alert multiple people when new rows are added.

How to Set It Up

1. Open your Google Form and click the Responses tab. Click the green Sheets icon to create a linked spreadsheet (or link to an existing one).
2. Open the linked Google Sheet.
3. Share the sheet with everyone who needs notifications. They need at least "Viewer" access.
4. Each person opens the sheet, clicks Tools > Notification settings (or Tools > Notification rules in older versions).
5. Set the notification to trigger when "A user submits a form" or "Any changes are made."
6. Choose between "Email - daily digest" and "Email - right away."

Limitations

• Not truly real-time. The "right away" option does not mean instant. Google's documentation states that notifications are sent "soon after" changes are made, and in practice the delay can range from a few minutes to over an hour during peak times.
• Daily digest is the default. If someone does not explicitly change the setting to "right away," they receive a single daily summary instead of individual notifications.
• Minimal email content. The notification email tells you that a change was made to the spreadsheet. It does not include the actual form response data in a readable format. Recipients have to click through to the sheet to see what was submitted.
• No filtering or routing. Like the collaborator method, everyone gets notified about every response. You cannot route notifications based on response content.
• Requires sheet access. Everyone who needs notifications must have access to the spreadsheet, which means they can also see all historical responses.

This method is best for situations where near-real-time is acceptable and the team is already working in the linked Google Sheet. For a deeper look at connecting forms to Google Sheets, see our guide on sending form data to Google Sheets automatically.

Method 3: Email Notifications for Google Forms Add-on (Popular, but Paid)

"Email Notifications for Google Forms" by Digital Inspiration is the most widely installed add-on for this purpose, with millions of users. It adds multi-recipient notifications, customizable email templates, and PDF attachments to Google Forms.

How to Set It Up

1. Open your Google Form.
2. Click the puzzle piece icon (Add-ons) in the top toolbar and search for "Email Notifications for Google Forms."
3. Install the add-on and grant it the required permissions (access to your form data and the ability to send email on your behalf).
4. Open the add-on from the puzzle piece menu and select "Create Email Notification."
5. In the notification configuration:
   • Enter multiple email addresses in the "Notify" field, separated by commas.
   • Customize the email subject and body using template variables like {{Full Name}} and {{Email}}.
   • Optionally attach a PDF summary of the response.
6. Save the notification rule.

Limitations

• Free tier is limited. The free version allows a small number of emails per day (the exact limit changes periodically but is typically around 20). For any form with meaningful volume, you need the paid plan.
• Paid plan costs roughly $30 per year. This is per Google account, not per form, so it covers all your forms. Reasonable for a single user, but costs add up across a team.
• Still no conditional routing. You can send to multiple addresses, but you cannot route specific responses to specific people based on the content of the submission. Everyone on the notification list receives every response.
• Add-on permissions are broad. The add-on requires access to your Google Drive, your Gmail (to send emails), and your form responses. Some organizations restrict add-on installations for this reason.
• Dependent on a third party. If Digital Inspiration discontinues the add-on or changes its pricing, your notification workflow breaks.

For a broader look at extending Google Forms with add-ons, see our roundup of Google Forms add-ons for 2026. The Email Notifications add-on is the most practical option for teams that need multi-recipient notifications without writing code, but it does not solve the conditional routing problem.

Method 4: Apps Script Custom Notifications (Free, but Technical)

Google Apps Script lets you write JavaScript that runs in response to form submissions. This is the most flexible free option, but it requires writing and maintaining code.

How to Set It Up

1. Open your Google Form.
2. Click the three-dot menu in the top-right corner and select "Script editor." This opens the Apps Script editor in a new tab.
3. Delete the default code and paste the following script:

function onFormSubmit(e) {
  var recipients = [
    "[email protected]",
    "[email protected]",
    "[email protected]"
  ];

  var responses = e.response.getItemResponses();
  var subject = "New Form Submission: " + e.response.getTimestamp();

  var body = "A new response was submitted.\n\n";
  for (var i = 0; i < responses.length; i++) {
    var item = responses[i];
    body += item.getItem().getTitle() + ": " + item.getResponse() + "\n";
  }

  for (var j = 0; j < recipients.length; j++) {
    MailApp.sendEmail({
      to: recipients[j],
      subject: subject,
      body: body
    });
  }
}

function installTrigger() {
  ScriptApp.newTrigger("onFormSubmit")
    .forForm(FormApp.getActiveForm())
    .onFormSubmit()
    .create();
}

4. Save the script (Ctrl+S or Cmd+S).
5. Run the installTrigger function once by selecting it from the function dropdown and clicking the play button. This sets up the trigger that fires onFormSubmit on every new submission.
6. Authorize the script when prompted. It needs permission to send email and access form responses.

Adding Conditional Routing

You can extend the script to send different emails to different people based on response content:

function onFormSubmit(e) {
  var responses = e.response.getItemResponses();
  var data = {};

  for (var i = 0; i < responses.length; i++) {
    data[responses[i].getItem().getTitle()] = responses[i].getResponse();
  }

  var subject = "New Form Submission: " + e.response.getTimestamp();
  var body = "A new response was submitted.\n\n";
  for (var key in data) {
    body += key + ": " + data[key] + "\n";
  }

  // Route based on department selection
  var department = data["Department"] || "";
  var recipients = [];

  if (department === "Billing") {
    recipients = ["[email protected]"];
  } else if (department === "Support") {
    recipients = ["[email protected]"];
  } else {
    recipients = ["[email protected]"];
  }

  // Always CC the manager
  for (var j = 0; j < recipients.length; j++) {
    MailApp.sendEmail({
      to: recipients[j],
      cc: "[email protected]",
      subject: subject,
      body: body
    });
  }
}

Limitations

• Daily email quota. Google limits Apps Script to 100 emails per day for free Gmail accounts and 1,500 per day for Google Workspace accounts. High-volume forms can hit this limit.
• Requires maintenance. When you add a new team member to the notification list, someone has to edit the script. When a field name changes, the conditional routing breaks silently.
• No error visibility. If the script fails -- due to a quota limit, a changed field name, or a permissions issue -- the form owner sees no indication. Responses are still collected, but notifications silently stop. You have to check the Apps Script execution log manually.
• No HTML email formatting. The basic MailApp.sendEmail sends plain-text emails. You can send HTML by using the htmlBody parameter, but building responsive HTML email templates in Apps Script is painful.
• Security review for new users. Google flags unverified scripts with a warning screen ("This app isn't verified"). This is normal for personal scripts but can alarm less technical team members who encounter it.

This method is best for teams with a developer who can write and maintain the script. It is the only free method that supports conditional routing, but it trades simplicity for flexibility.

Method 5: Zapier or Make (Most Flexible, but Expensive)

Automation platforms like Zapier and Make can connect Google Forms to virtually any email service, Slack channel, CRM, or notification tool. This is the most powerful option, but it comes with ongoing costs.

How to Set It Up (Zapier Example)

1. Create a Zapier account and start a new Zap.
2. Set the trigger to "Google Forms: New Response in Spreadsheet." (Zapier reads form responses from the linked Google Sheet, not directly from the form.)
3. Add an action step: "Gmail: Send Email" or "Email by Zapier: Send Outbound Email."
4. Configure the email recipients, subject line, and body. Use Zapier's field mapping to insert form response data into the email template.
5. To send to multiple recipients, either enter multiple addresses in the "To" field (comma-separated) or add multiple email action steps for different routing rules.
6. Turn on the Zap.

Adding Conditional Routing

Zapier supports "Filter" and "Paths" steps that let you route submissions based on field values. For example, you can create a Path where billing inquiries go to [email protected] and support requests go to [email protected]. Each path has its own email action with different recipients, subject lines, and templates.

Limitations

• Cost. Zapier's free tier allows 100 tasks per month (each form submission counts as one task). Paid plans start at $20 per month for 750 tasks. Make is cheaper but has a steeper learning curve.
• Latency. On Zapier's free and lower-paid tiers, Zaps check for new data every 15 minutes. Instant triggers require a paid plan.
• Complexity. Setting up conditional routing with Paths creates a multi-step Zap that can be difficult to debug and maintain. Each path adds to your task count.
• Two tools to manage. You are now maintaining both your Google Form and your Zapier account. If your Zapier subscription lapses or a connection breaks, notifications stop silently.
• Overkill for simple cases. If all you need is "send the same email to five people," Zapier is a heavyweight solution for a lightweight problem.

This method makes sense when you are already using Zapier for other automations and the marginal cost of adding one more Zap is low. For teams starting from scratch, the cost and complexity are hard to justify for email notifications alone.

Comparison: All Five Methods Side by Side

No single method checks every box. The free options either require manual opt-in, lack real-time delivery, or demand coding skills. The paid options solve the core problem but introduce ongoing costs and external dependencies.

When You Need Conditional Email Routing

The comparison table above highlights a critical gap: conditional routing. Most teams eventually need it, and most methods cannot provide it.

Conditional routing means sending different notifications to different people based on the content of the submission. Common examples:

• Billing inquiries go to [email protected]
• Support requests go to [email protected]
• Partnership proposals go to [email protected]
• Enterprise leads (budget over $50K) go directly to the VP of Sales
• Urgent issues (priority marked "High") go to the on-call team's Slack channel and email

In Google Forms, building conditional logic is already constrained to section-level branching. Adding conditional email routing on top of that requires either a custom Apps Script (Method 4) or an external automation tool (Method 5). Neither integrates cleanly with the form itself -- the routing logic lives outside the form, in a separate script or a separate platform, making it difficult to see the full picture of what happens when someone submits a response.

This is the problem that drives teams away from Google Forms entirely. The form collects data fine. But getting that data to the right person, at the right time, based on what was submitted -- that is where Google Forms and its ecosystem of workarounds fall short.

How Buildorado Handles Multi-Recipient Notifications

Buildorado takes a different approach. Email notifications are not a bolt-on feature or an add-on -- they are a workflow node that sits on the same canvas as your form, your conditional logic, and your integrations.

Built-in Email Node

When you create a workflow in Buildorado, you can drag an Email node onto the canvas and connect it to your form's submission output. The Email node lets you:

• Send to multiple recipients. Enter as many email addresses as you need, separated by commas. No per-recipient limits, no opt-in required.
• Customize the email template. Use template variables to insert form field values into the subject line and body. {{full_name}}, {{email}}, {{message}} -- every field on your form is available as a variable.
• Attach a formatted summary. Include a styled summary of the submission in the email body without writing HTML by hand.

Conditional Routing on the Same Canvas

Here is where Buildorado diverges from every method listed above. You can add condition nodes between your form and your email nodes to route submissions to different recipients based on any field value.

A practical example: you have a contact form with a "Department" dropdown. On the Buildorado canvas, you connect the form to a condition node that checks the Department field. From the condition node, three branches lead to three Email nodes:

• "Billing" routes to [email protected]
• "Support" routes to [email protected]
• Everything else routes to [email protected]

The entire routing logic is visible on a single canvas. No scripts to maintain, no external tools to pay for, no hidden configuration buried in an add-on's settings panel. If you need to add a new department or change a recipient, you edit the condition node directly.

For teams building more complex notification workflows, Buildorado supports branching on any field type -- text, number, date, dropdown, checkbox -- using 35+ comparison operators. You can combine conditions with AND/OR groups, and you can chain multiple condition nodes for deeply nested routing.

No Add-ons, No Per-Email Pricing

Buildorado's email notifications are included in the platform. There is no add-on to install, no separate email quota to manage, and no per-message pricing. The free tier includes email notifications, and paid plans increase volume limits alongside everything else.

Build Your Notification Workflow

If you are managing Google Form notifications with add-ons, scripts, or Zapier, you are spending time and money on infrastructure that should be built into your form tool. Buildorado gives you multi-recipient notifications, conditional routing, and customizable templates on the same canvas where you build your form -- no middleware required.

Try Buildorado free and set up your first notification workflow in under five minutes. No credit card required.