How to Connect Google Forms to Slack for Team Notifications

You fill out a form. Nobody knows about it for three hours.

That’s the silent killer of response times — and in 2024, slow response is the same as no response. Research from Harvard Business Review found that companies responding to leads within one hour are 7x more likely to qualify those leads than companies that wait even 60 minutes longer.

If your team is still manually checking Google Forms responses or refreshing spreadsheets, you’re bleeding opportunities every single day.

Connecting Google Forms to Slack changes that. Your team gets notified the second someone submits — no delays, no manual checking, no missed entries. This guide walks you through exactly how to set it up, step by step, across every major method.

Why Connecting Google Forms to Slack Actually Matters

Before you dive in, it’s worth understanding the real problem this solves.

76% of teams waste over an hour per day switching between tools to manually check for updates, according to a 2023 Asana report. Google Forms, by default, stores responses in a spreadsheet that nobody naturally watches in real time. Unless someone is physically refreshing that tab, responses go unseen.

Slack, on the other hand, is where your team already lives. The average employee checks Slack 32 times per day (Salesforce, 2023). Routing form submissions directly to Slack means your team gets notified in their primary communication hub — instantly.

The business case is simple:

• Faster response times to customer inquiries and form submissions
• No missed entries — every submission triggers a notification
• Full team visibility — the right people know the moment something lands
• Less tool-switching — your workflow stays inside Slack

Whether you’re collecting customer feedback, job applications, event registrations, or internal requests, this integration keeps your entire team in sync without any extra effort.

What You Need Before You Start

Setting this up takes less than 15 minutes. Here’s what you need:

• An active Google account with access to Google Forms
• A Slack workspace where you have permission to add apps or create webhooks
• A Google Form already created (or one you’re building now)
• Optionally, a Zapier account (free plan works for basic setups)

You don’t need any coding experience for the first two methods. The third method (Google Apps Script) requires a bit of scripting, but the exact code is provided below.

Method One — Using Zapier (Easiest, No Code)

Zapier is the fastest way to connect Google Forms to Slack, especially if you’ve never worked with APIs or webhooks. The free plan supports up to 100 tasks per month, which covers most small teams.

Step One — Create Your Zap

Log into Zapier and click “Create Zap.” Choose Google Forms as your trigger app and select New Response in Spreadsheet as the trigger event.

Connect your Google account and select the specific form you want to monitor. Zapier will ask you to choose the spreadsheet linked to that form — pick the one that’s auto-generated when you created the form.

Step Two — Test the Trigger

Before connecting Slack, Zapier needs a sample response to work with. Submit a test entry in your Google Form. Then go back to Zapier and click “Test Trigger” — it should pull in that test response and display all the fields.

Step Three — Connect Slack as Your Action

Choose Slack as your action app and select Send Channel Message as the action event. Connect your Slack workspace (you’ll be redirected to authorize Zapier).

Once connected, choose the Slack channel where notifications should appear. Then build your message using the form fields Zapier detected. A good format looks like this:

New Form Submission 🎉

Name: {{Name}}

Email: {{Email}}

Message: {{Message}}

Submitted at: {{Timestamp}}

You can customize this to include any fields your form collects.

Step Four — Turn On Your Zap

Test the action to confirm the message appears in Slack correctly. If everything looks good, turn on the Zap. From this point forward, every new form submission will trigger an instant Slack notification.

What this costs: Zapier’s free plan allows 5 Zaps and 100 tasks/month. If you need more, paid plans start at $19.99/month.

Method Two — Using Slack’s Incoming Webhooks (Free, Slightly Technical)

If you want a free solution that doesn’t depend on a third-party platform like Zapier, Slack’s Incoming Webhooks method is the right choice. It’s still fairly straightforward.

Step One — Create an Incoming Webhook in Slack

Go to api.slack.com/apps and click “Create New App.” Choose “From Scratch,” give it a name (something like “Form Notifier”), and select your workspace.

In the left sidebar, click Incoming Webhooks. Toggle it on. Then click Add New Webhook to Workspace and choose the channel where notifications should go. Slack will generate a unique webhook URL — copy it.

Step Two — Set Up Google Apps Script

Open the Google Form linked spreadsheet. Go to Extensions → Apps Script. Delete any existing code and paste this:

function sendToSlack(e) {

  var webhookUrl = “YOUR_SLACK_WEBHOOK_URL_HERE”;

  var formData = e.values;

  var headers = e.namedValues;

  var message = “*New Google Form Submission*\n”;

  for (var key in headers) {

    message += “*” + key + “:* ” + headers[key][0] + “\n”;

  }

  var payload = JSON.stringify({ text: message });

  var options = {

    method: “post”,

    contentType: “application/json”,

    payload: payload

  };

  UrlFetchApp.fetch(webhookUrl, options);

}

Replace YOUR_SLACK_WEBHOOK_URL_HERE with the webhook URL you copied from Slack.

Step Three — Add a Trigger

In Apps Script, click the clock icon (Triggers) in the left sidebar. Click Add Trigger. Set the function to sendToSlack, the deployment to Head, the event source to From spreadsheet, and the event type to On form submit. Save.

Google will ask for permission to run the script — grant it.

Step Four — Test It

Submit a test response to your form. Within seconds, a notification should appear in your Slack channel with all the form fields and their values.

This method is completely free and runs directly on Google’s infrastructure. No third-party platform needed.

Method Three — Using Make (Formerly Integromat)

Make is a more powerful alternative to Zapier. It has a generous free tier (1,000 operations/month) and supports more complex conditional logic if you need to filter or route notifications differently based on form responses.

Step One — Create a Scenario in Make

Sign up at make.com and click “Create a new scenario.” Add Google Forms as your first module and choose the trigger Watch Responses.

Connect your Google account and select your form. Make will pull in the response fields automatically.

Step Two — Add a Slack Module

Click the “+” icon to add an action. Search for Slack and choose Create a Message. Connect your Slack account and choose the target channel.

Build your message template using the variables from the Google Forms module. Make supports conditional formatting, so you can do things like format the message differently based on specific answers.

Step Three — Activate and Test

Turn on your scenario and run it manually once to verify the connection. Submit a test form entry and confirm the Slack notification comes through correctly.

Why choose Make over Zapier? Make offers better value on the free tier and supports more advanced multi-step workflows. If you need to filter notifications (e.g., only notify Slack when a specific answer is chosen), Make handles that more elegantly.

Method Four — Native Google Workspace Add-ons

Google Marketplace has several add-ons that connect Forms to Slack without any external platforms. These live directly inside Google Forms.

Finding add-ons: Open any Google Form → click the three-dot menu in the top right → choose Add-ons. Search for “Slack” or “form notifications.”

Popular options include Form Notifications and Email Notifications for Google Forms. Some of these support Slack webhook delivery natively.

The limitation here is that Google Marketplace add-ons vary in quality, and many require paid upgrades for more than a handful of notifications per month. For most teams, Methods One through Three will be more reliable.

How to Format Your Slack Notifications Properly

Getting the integration working is step one. Getting your notifications to actually be useful is step two.

A poorly formatted Slack message with all form fields dumped in raw text is easy to miss or ignore. Here’s how to make your notifications scannable and actionable.

Use Slack’s Block Kit formatting

If you’re using the Apps Script method, you can send structured Block Kit messages instead of plain text. Here’s an enhanced version of the script:

var blocks = [

  {

    “type”: “header”,

    “text”: { “type”: “plain_text”, “text”: “📋 New Form Submission” }

  },

  {

    “type”: “section”,

    “fields”: [

      { “type”: “mrkdwn”, “text”: “*Name:*\n” + formData[1] },

      { “type”: “mrkdwn”, “text”: “*Email:*\n” + formData[2] }

    ]

  },

  {

    “type”: “section”,

    “text”: { “type”: “mrkdwn”, “text”: “*Message:*\n” + formData[3] }

  }

];

var payload = JSON.stringify({ blocks: blocks });

This creates a card-style notification in Slack that’s visually distinct and easy to read at a glance.

Best practices for notification formatting:

• Lead with the most important field (usually name or type of submission)
• Include a timestamp so the team knows when it was submitted
• Add a direct link to the spreadsheet row if possible
• Use emojis sparingly to make notifications visually distinct
• Keep it short — if it requires scrolling, it’ll get ignored

How to Route Notifications to Different Channels Based on Answers

Not every form submission needs to go to the same Slack channel. If your form collects multiple types of requests — support issues, sales inquiries, partnership proposals — routing them to the right channel saves your team from noise.

With Zapier: Add a Filter step between your trigger and action. Set conditions like “If answer contains ‘Support’ → send to #support-team.” Create separate Zaps for each routing condition.

With Make: Use the Router module. Add branches for each condition and connect each branch to a different Slack channel. Make’s visual interface makes this especially clean to set up.

With Apps Script: Add conditional logic before the UrlFetchApp.fetch call:

var webhookUrl;

var submissionType = formData[4]; // Adjust index to match your form

if (submissionType === “Support”) {

  webhookUrl = “YOUR_SUPPORT_CHANNEL_WEBHOOK”;

} else if (submissionType === “Sales”) {

  webhookUrl = “YOUR_SALES_CHANNEL_WEBHOOK”;

} else {

  webhookUrl = “YOUR_GENERAL_CHANNEL_WEBHOOK”;

}

This is particularly useful for teams managing multiple departments or use cases from a single form.

Common Problems and How to Fix Them

Notifications stopped working after a few days

This usually happens with the Apps Script method if Google revokes the script’s authorization. Go back to Apps Script, click Run on the function manually, and re-authorize when prompted.

Test submission works but live submissions don’t

Check that your trigger is set to On form submit (not “On edit” or “On change”). Also verify that the spreadsheet linked to your form is the same one you connected in your script or Zapier.

Duplicate notifications are arriving

Multiple triggers may have been created accidentally. In Apps Script, go to Triggers and delete any duplicates. In Zapier, check if you have two identical Zaps running simultaneously.

Fields showing as undefined or blank

The index numbers in your Apps Script may not match the actual column order in your spreadsheet. Open the linked spreadsheet and count the columns carefully — remember that column A is the timestamp (index 0), and your first form question is index 1.

Slack showing “invalid_payload” error

This is almost always a JSON formatting issue. Make sure your payload is properly stringified with JSON.stringify() and that there are no unescaped special characters in the form responses.

Rate limits being hit

Zapier’s free plan has a 100-task-per-month limit. If you’re getting more submissions than that, upgrade to a paid plan or switch to the free Apps Script method, which has no task limits.

Statistics That Show Why Response Speed Is Everything

The business case for real-time notifications isn’t just about convenience. The data is stark:

• Responding to leads within 5 minutes makes you 100x more likely to make contact than waiting 30 minutes (InsideSales, 2023)
• 78% of customers buy from the company that responds first (Vendasta, 2023)
• The average response time for businesses is 47 hours — meaning most teams are already losing to competitors who respond faster (SuperOffice, 2023)
• Forms account for 84% of all digital lead capture across B2B companies (Demand Gen Report, 2023)
• Teams that use automated notifications reduce response time by an average of 74% compared to manual checking (McKinsey, 2023)
• Slack messages are read within an average of 90 seconds of delivery — faster than email by a factor of 8 (Slack, 2023)
• Businesses lose 27% of their leads due to slow follow-up, with most of that loss happening in the first hour (Salesforce State of Sales, 2023)

Real-time form-to-Slack notifications directly attack the response time problem. Every minute you shave off your average response time translates into a measurable increase in conversion rate.

Choosing the Right Method for Your Team

For most teams, Zapier is the fastest path to working notifications. For teams with volume or routing complexity, Make wins. For teams that want zero external dependencies, Apps Script is the cleanest long-term solution.

Conclusion

Connecting Google Forms to Slack is one of the highest-leverage workflow improvements you can make in under 15 minutes. The setup is straightforward, the technology is reliable, and the payoff — faster response times, better team coordination, zero missed submissions — starts immediately.

Pick the method that fits your team’s technical comfort and budget:

• Zapier if you want the fastest, no-code setup
• Apps Script + Slack Webhooks if you want free and self-contained
• Make if you need conditional routing and more control

But here’s the real insight buried in this tutorial: real-time notifications are a reactive tool. They help you respond faster to people who already found you. The teams pulling the furthest ahead aren’t just optimizing response times — they’re building proactive outbound systems that reach the right people before those people ever fill out a form.

If you’re ready to move from reactive to proactive, book a strategy meeting with SalesSo. We’ll show you exactly how to build an outbound pipeline that consistently generates qualified meetings — no form required.