CentriWebGoogle Sheets automation is a good first step for a small business: a form fills a sheet, a script sends a reminder, and a connector copies a row into another tool. It stops being enough when more than a couple of people depend on the sheet, when a missed row costs you a customer, or when you spend more time repairing it than using it. This article covers what you can automate, the limits Google publishes, and the signs that it is time to move on.
It is written for owners and managers who built a sheet that now runs part of the business, often a booking list, a lead tracker or a job board. We opened Google’s own pages for the figures below, in November 2026. Google can change them, so check the linked pages.
What Google Sheets automation can do
There are three levels, in rising order of effort.
Built-in features. Notification rules, filters, conditional formatting and data validation all work without code. Validation matters more than people think: a drop-down for status stops “Done”, “done” and “Completed” becoming three different values that break every report.
Scripts inside the sheet. Google Apps Script lets you write small programs that run on a schedule or when someone edits a cell or submits a form. Common uses are sending an email when a status changes, copying finished rows to an archive tab, or creating a calendar event from a booking.
Connecting to other tools. Automation platforms such as Zapier, Make and n8n can watch a sheet for new rows and pass them on, or write rows into it from a form, a CRM or a payment tool. Our comparison of Zapier, Make and n8n explains how each charges, and CentriWeb builds most client automations in n8n.
A tidy example for a clinic or practice: a web enquiry form writes a row, a script emails the front desk, and a status column drives a reminder. It works, and for a small volume it is a sensible way to start.
The limits Google publishes
Google lists quotas for Apps Script, which is what most automation inside a sheet uses. According to Google’s Apps Script quotas page, as at November 2026:
| Limit | Consumer account (such as gmail.com) | Google Workspace account |
|---|---|---|
| Script runtime per execution | 6 minutes | 6 minutes |
| Total trigger runtime per day | 90 minutes | 6 hours |
| Email recipients per day | 100 | 1,500 |
Google notes that quotas and limitations may change. Check the page for the current numbers.
What does that mean in practice? A script that sends reminder emails from a free Gmail account tops out at 100 recipients a day. A script that loops over thousands of rows can hit the six minute limit and stop partway, which is a quiet failure: some rows are processed and some are not, and nothing tells you.
Sheet size has a limit too. Google’s file limits page says spreadsheets created in or converted to Google Sheets can hold up to 20 million cells. Most small businesses will not reach that, but a sheet with many formulas that look up other tabs can become slow to open long before that, in our experience.
A worked example with made-up numbers
Suppose a physio clinic sends appointment reminders from a script on a free Gmail account, and it books 70 people on a busy day. With a limit of 100 email recipients a day, that leaves 30 emails for everything else the account sends, including replies to enquiries. Add a second reminder to each patient and the script reaches the limit before lunch. Nobody gets an error. The reminders just stop. The numbers are an example, so count your own sends, but the lesson holds: know your daily volume and compare it with the quota before you rely on a script.
Where Google Sheets automation works well
- One owner, one purpose. A single person updates it, and it answers one question, such as which quotes are outstanding.
- Low volume. A few dozen rows a week, where you would notice if something went missing.
- Short chains. A new row triggers one action, such as an email to you.
- A trial run. You are working out what the process should be before you pay for a system. A sheet is a cheap way to find that out.
If that describes you, do not move yet. Spend an hour adding validation, protect the formula columns and write down what each column means.
Signs it is time to move on
These are the patterns we see when a sheet has become the whole system.
- Two people edit at once and something goes missing. Someone overwrites a row, or a filter hides data that a colleague then does not see.
- Only one person understands it. If that person is away, nobody dares touch the formulas.
- You copy data between tabs or files by hand. This is the work that automation was meant to remove.
- Automations fail without anyone knowing. A script hits its limit, a connection expires, and the first sign is a customer who never got a message.
- You need different people to see different things. A sheet shares everything or nothing. Hiding tabs is not a safe way to protect customer data.
- You need a record of who did what. If you need to know who changed a price or who contacted a lead, a sheet is a weak answer.
- The sheet takes a long time to open. Slow load is often the first physical sign that it has outgrown its job.
Two or three of these together is a good signal. One alone is usually fixable. Our guide on CRM vs spreadsheet covers the same decision from the customer-tracking side.
Google Sheets to CRM: what to move first
Do not move everything at once. Pick the part of the sheet that costs the most when it fails, and move that.
For most businesses that is the customer or lead list, because that is where a missed follow-up costs money. A CRM keeps one record per person, shows who owns it, and can send reminders without a script that runs out of time. Keep the rest in the sheet until it also hurts.
Before you move, clean the data: one row per person, one format for phone numbers, one set of status words. Import a copy first and check a sample of records against the sheet. Keep the sheet read-only for a few weeks as a backup, and name a date after which no one updates it.
If the sheet is more than a customer list, such as a job tracker with its own rules and calculations, a CRM may not fit it. That is where replacing a spreadsheet with an app comes in, and we discuss the trade-offs there.
Keeping a Google Sheets workflow reliable in the meantime
If you are staying with the sheet for now, a few habits keep it dependable:
- Use a Google Workspace account for anything that sends email or runs scripts daily. The published limits above are higher for Workspace than for consumer accounts.
- Have scripts email you when they fail. A script that fails silently is worse than none.
- Keep a log tab recording each automatic action, with a date and the row it applied to.
- Limit who can edit. Give most people view or comment access, and one or two people edit access.
- Test with a copy before changing a formula or script that the business depends on.
Automations built on a sheet break for ordinary reasons: someone renames a column, a connection needs signing in again, a limit is hit. Our guide on why automations break lists what to check.
When a custom system is the better step
When a sheet has become the place where leads, bookings and follow-up all live, you have outgrown it in most cases. CentriWeb sets up CRM and custom software and moves the data across, starting with the part that costs you most. We would not recommend it to a business with a handful of rows a week, an owner who enjoys the sheet, or a process that is still changing every month. For those, the sheet is the right tool.
For a clinic or practice that wants to see how this looks with enquiries, our web form to CRM guide shows the steps, and the automation topic page lists the rest.