Google Sheets Automation: Apps Script, CRM and Website Links
How to automate Google Sheets with formulas, Apps Script triggers and n8n, Zapier or Make, connect it to your CRM and website, and know when to move to a CRM.

Google Sheets automation works on three levels. Formulas such as QUERY and IMPORTRANGE keep data in sync without copy-paste, Google Apps Script runs code on triggers to send alerts, build reports and accept website leads, and outside tools (webhooks, Zapier, Make or n8n) connect the sheet to your CRM, Stripe and Slack. For a small team this setup can run for years. Once several people work the same deals in one sheet, it starts losing data, and the process belongs in a CRM, with Sheets kept for reporting.
What you can automate in Google Sheets
Most manual spreadsheet work follows the same pattern: copy, check, calculate, tell someone. Google gives you four built-in ways to remove it before you pay for anything.
- Formulas. IMPORTRANGE pulls a range from another spreadsheet, QUERY filters and groups data with SQL-like syntax, and ARRAYFORMULA applies one calculation to a whole column, so new rows are covered automatically. This is enough for a summary of several locations or sales reps in one file.
- Google Forms. Every response lands as a new row in a linked sheet: intake forms, internal requests, quote requests, customer surveys.
- Google Apps Script. A JavaScript-based platform built into Google Workspace. A script can read and write cells, send email, generate Docs and PDFs from a template, call external APIs over HTTP and even publish a small web endpoint that receives data.
- Add-ons. Ready-made extensions from the Google Workspace Marketplace for imports, mail merge and data connectors. Quick for a single task, but you depend on a third-party vendor and its pricing.
Typical use cases we see in small and mid-size companies:
- website leads written to a sheet as a log next to the CRM;
- a scheduled report emailed to the owner every morning at 8:00;
- a Slack or email notification when a row's status changes to "Approved" or "Overdue";
- a nightly pull of deals from the CRM, payouts from Stripe or spend from ad platforms into a sheet for custom calculations such as commissions or plan vs actual.
Google Apps Script triggers: simple vs installable
Triggers are what turn a script into automation: the code runs by itself when something happens. There are two kinds, and mixing them up is the most common reason a script "works when I run it" but not on its own.
- Simple triggers are reserved function names like
onEdit(e)oronOpen(e). They need no setup, but per Google's documentation they can't run longer than 30 seconds and can't use services that require authorization. A simpleonEditcan stamp a timestamp or validate input, but it cannot send an email through Gmail. - Installable triggers are created in the script editor or in code and run with the authority of the person who created them. They can send email, call APIs and work with other files. Use them for an installable
onEdit,onFormSubmit(a new Google Forms response) and time-driven runs: every hour, every day at 8:00, every Monday.
Two details catch teams later. First, neither kind fires on changes made by another script or by an API request. If an integration writes leads into the sheet, onEdit will never see them, so the logic has to run on a timer or inside the integration itself. Second, an installable trigger belongs to one person's account. When that employee leaves and their account is suspended, the reports quietly stop. Create triggers from a shared service account or an admin account, and keep a short note on what each script does and who owns it.
Apps Script quotas and Google Sheets limits
Both Sheets and Apps Script have hard limits, and the free consumer account and Google Workspace differ a lot. At the time of writing, Google's official pages list these values:
- up to 20 million cells or 100MB per spreadsheet created in or converted to Google Sheets;
- 6 minutes per script execution and 30 seconds per custom function, on any account;
- 20 triggers per user per script;
- total trigger runtime: 90 minutes per day on a consumer account, 6 hours per day on Google Workspace;
- URL Fetch calls (requests to external APIs): 20,000 per day for consumer accounts, 100,000 for Workspace;
- email recipients sent by script: 100 per day for consumer accounts, 1,500 for Workspace;
- Sheets API for outside tools: 300 read and 300 write requests per minute per project, 60 per minute per user.
In practice teams rarely hit the cell limit. They hit speed first. A file with tens of thousands of rows, five IMPORTRANGE sources and heavy QUERY formulas opens slowly, and a script that loops row by row instead of reading the range in one call runs out of its 6 minutes. A business that runs real automation on a personal Gmail account also hits the 100-recipient email cap fast. Quotas change, so check the current page before you build something critical.
Google Sheets as a CRM: when it is enough and where it breaks
Using Google Sheets as a CRM is a reasonable start: it is free, everyone knows it, and there is nothing to implement. It is enough when:
- one or two people handle leads, and volume is a few dozen a month;
- the sales cycle is short and nobody needs a history of calls and emails;
- you need a simple list: client, contact, status, value, owner, next step.
It breaks in predictable places:
- Concurrent edits. Two reps sort or filter the same tab, and one overwrites the other's row. Version history helps, but restoring is manual, and nobody notices for a week.
- No deal history. A row stores the current state, not the chain of calls, emails and reschedules. A month later nobody can tell who promised what.
- Permissions. Hiding other reps' clients or a margin column takes protected ranges and separate files. Anyone with edit access can download the whole client base.
- No tasks or reminders. Follow-ups get bolted on with scripts, and each script is one more thing that fails silently.
- Limits. As the base grows, the file slows down and formulas start showing loading errors.
If two or more of these sound familiar, move deals into a real CRM and keep Sheets for plans, targets and analysis.
How to connect Google Sheets to a CRM, your website and Slack
A sheet rarely lives alone. The common connections:
- Website forms. The form submits to the CRM and also writes a row to a sheet as a backup log. An Apps Script web app with a
doPostfunction can accept the request directly, but it does not expose request headers, so you cannot verify the signatures many services send. For anything beyond a simple form, put a proper automation layer in front. - HubSpot, GoHighLevel, Salesforce. All three send events (new contact, stage change, closed deal) through workflows or webhooks and expose data through their APIs. GoHighLevel workflows can write rows to Google Sheets natively, and both HubSpot and Salesforce have Sheets integrations or connectors. The typical goal is an export for your own math: commissions, source reports, forecasts.
- Slack and email. A new row or a status change posts a message to a channel; a daily digest goes to the team lead.
- Stripe and ad platforms. Payments, refunds and daily spend pulled on a schedule, so finance numbers sit next to sales numbers.
You can write all of this in Apps Script, but the code grows fast, failures go to an inbox nobody reads, and the quotas cap the scale. This is where low-code tools come in, and there are three serious options.
- Zapier has the largest app catalog and the gentlest learning curve. It bills per action step, so long workflows at volume get expensive.
- Make offers a visual scenario builder with routers and iterators, more flexible than Zapier for branching logic, billed per module action.
- n8n runs in n8n's cloud or self-hosted on your own server. It bills per workflow execution, not per step, and the self-hosted version has no per-run fee at all, only hosting costs. Code nodes let you write JavaScript or Python inside the flow, so the edge cases that would push you back to Apps Script stay in the same tool, with execution logs and retries built in. For teams with steady volume or sensitive data, it is often the most practical choice.
We usually build these flows in n8n automation projects, and when several systems have to work as one chain, through broader integrations and automation work.
Formulas vs Apps Script vs Zapier/Make vs n8n vs a CRM
| Option | What it solves | Upkeep cost | When to pick |
|---|---|---|---|
| Formulas (QUERY, IMPORTRANGE, ARRAYFORMULA) | Summaries and calculations inside Google | Near zero | Data is already in sheets, you need a report |
| Apps Script | Alerts, emails, documents, scheduled reports | Needs someone who reads code | Logic stays inside Google, low volume |
| Zapier or Make | Sheets linked to the CRM, forms, Slack | Subscription grows with steps and volume | Non-technical owner, niche apps, small volume |
| n8n (cloud or self-hosted) | Same links plus custom logic in code nodes | Per execution or hosting only, needs light tech support | Three or more systems, higher volume, data control |
| Move the process into a CRM | Deals, history, permissions, tasks | CRM subscription and setup | Several people work with clients daily |
Our decision rule
Look at where the data lives and how many people change it:
- Data is already in sheets and you need a summary: use formulas, no scripts.
- You need an action on an event or schedule inside Google (email, document, report): use Apps Script with installable triggers, error logging and a named owner.
- The sheet exchanges data with the website, CRM, Stripe or Slack: move the connection into n8n, Make or Zapier instead of a growing script. Pick n8n when volume is steady or flows need custom code, Zapier or Make when the owner wants to edit flows alone.
- Three or more people work with clients in the sheet, or you need deal history: move the process into a CRM and keep Sheets for analytics.
Before any automation, clean up the sheet itself: one tab per entity, one row per record, no merged cells, and a real status column instead of colored rows. Scripts and integrations run for years on that structure and break on the first edit of a messy one. If you want a second pair of eyes on your sheets, scripts or CRM connection, see how we handle Google Sheets automation.
Yes. Apps Script is included with every Google account and Google Workspace plan at no extra cost. What you pay for is the account tier: Workspace raises the daily quotas, for example trigger runtime from 90 minutes to 6 hours per day and email recipients from 100 to 1,500.
Apps Script triggers fire only on edits made by a person in the sheet. Rows added by another script or through the Sheets API do not trigger onEdit. Use an onFormSubmit trigger for Google Forms, a time-driven trigger that checks for new rows, or run the logic inside the integration that writes the data.
For one or two people with a short sales cycle, often yes. It stops working when several reps edit the same rows, when you need a history of calls and emails per deal, or when reps should only see their own clients. At that point a CRM with Sheets as a reporting layer is the safer setup.
The simplest route is a webhook from the form to an automation tool (n8n, Make or Zapier) that appends a row and creates the CRM record in the same flow. An Apps Script web app can also receive the submission directly, which suits low volume and forms that do not require signature checks.
How we can help
- Google Sheets & spreadsheetsWe sync your CRM, website and tools with Google Sheets: data updates itself, no copy-pasting
- n8n automationn8n workflows: integrations, data sync and AI agents on your own server
- Integrations & automationWe connect your website, CRM, ads and tools so data flows on its own and scripts and AI handle the routine



