Skip to content
← All articles
8 min read

Google Sheets integration: when a spreadsheet works as a database and when it doesn't

Google Sheets works as a database for small data volumes, one or two writers and a process that people run anyway. It breaks where you need concurrent writes, strict data rules, role-based access and frequent requests: the Sheets API has per-minute request quotas. Below: when a sheet is enough, what exactly breaks, and how to move to a real database without stopping the work.

Why businesses integrate with Google Sheets

A spreadsheet is the most familiar tool there is: orders, customers, stock and reports already live in one. Staff know how to work in it, nothing needs installing, and a column changes in a second. So the first automation is almost always built around it: a website form writes leads to a sheet, a bot reads the price list, a report is assembled from rows.

That is a sound start. Trouble begins when the sheet turns from a convenient tool into the only data store a business process depends on. Then the integration has to respect how sheets behave instead of treating one as an ordinary database.

When Google Sheets is enough

Sheets work well while data is small, one or two sources write to them, and a person can open the file at any moment and see what is going on. Visibility for staff is the main advantage, and in many processes it matters more than database strictness.

A good sign: if you can afford to lose the last few minutes of data or fix a mistake by hand, a sheet will cope. A bad sign: an error costs money and is found too late.

  • A small volume of data that is easy to scan by eye.
  • One or two writers, such as a form and a manager.
  • A process people already run, where automation only appends or reads rows.
  • A prototype or first version where you need to test an idea fast.
  • Reports and dashboards where the sheet is a display, not the source of truth.

Sheets API limits to know in advance

The Google Sheets API has quotas. According to the official documentation: 300 read and 300 write requests per minute per project, and 60 read and 60 write requests per minute per user per project. There is no daily cap as long as you stay within the per-minute quotas. Going over returns a 429 error, and Google recommends retrying with exponential backoff. Check current values in the documentation, as they can change.

For an integration this means three things. You cannot make a request per event: updates should be grouped, since a batch request counts as one request. You cannot read the sheet on every user request: you need a cache. And you need a queue with retries so a burst of leads does not get lost to a 429. The documentation recommends keeping a single request to about 2 MB.

  • Group changes into batch requests instead of writing one cell at a time.
  • Cache what you read for a short time.
  • Queue writes and retry with growing delays on 429. See background jobs and queues.
  • Keep the sheet out of the user-facing request path: nobody should wait on the Sheets API.

Concurrent writes and lost data

A sheet has no transactions. If two processes read at once, change their own copy and write back, the last one overwrites the first. If an integration updates a row by its number and someone sorts the sheet or deletes a row, that number now points to a different record.

Discipline solves this: append new data instead of editing existing rows; give each record its own unique ID in a column and look it up by that, not by row number; make one service the single writer for its area. Redelivered events must not create duplicates: see idempotency and retries.

No schema, so data rots quietly

A sheet does not know that the "Phone" column should hold a phone number or that "Amount" should be numeric. Someone types text into a numeric column, renames a header or inserts a column in the middle, and the integration starts reading the wrong data or fails. The error does not show up right away.

The defense is validating input at the integration boundary: expected headers, types, required fields. Anything that fails the check must not pass silently: log it and notify the owner. For critical data, protect ranges against manual editing.

Access control and security

Permissions in a sheet are set at the file, tab or range level, but not per row by rules such as "a manager sees only their own clients". If the sheet holds personal customer data, anyone with access to the file sees all of it.

The integration should run under its own account (a service account) with the minimum rights, and keys must not live in code or in the sheet. Review who has access to the file from time to time and remove people who no longer need it. General integration security is covered in webhook signatures.

When to move to a database

Signs the sheet has become the bottleneck: you hit quotas, records get lost or duplicated, you need role-based access, you want to link data together, formulas have become heavy and slow, or you fear someone will accidentally break the structure.

The move does not have to be abrupt. A working setup: data lives in a database (for example PostgreSQL), and the sheet stays as a convenient interface: reports are exported to it and, when needed, edits come back through a validated entry point. Staff keep working in the familiar view while the database becomes the source of truth. How to move data without losing it is in CRM data migration.

  • Migrate step by step: copy the data first, run in parallel, then switch over.
  • Keep the sheet for reports and manual edits through a validated entry point.
  • Back up the database and test restores: PostgreSQL backups.
  • If you want to automate the whole process, see our integrations service.
Questions

FAQ

Didn't find an answer — ask on the call or in Telegram.

Can I use Google Sheets as a database?

For small volumes and one or two writers, yes. For concurrent writes, strict data rules, role-based access and frequent requests it is a poor fit: a sheet has no transactions or schema, and the API has per-minute request quotas.

What are the Google Sheets API limits?

Per the official documentation: 300 read and 300 write requests per minute per project, 60 of each per user per project, and no daily cap. Exceeding them returns a 429 error and you should retry with exponential backoff. Values can change, so check the documentation.

How do I connect a website or bot to Google Sheets?

Through the Sheets API using a service account with minimal rights: the site or bot sends data to your server and the server appends rows in batches. Keep keys out of the code and write through a queue with retries so a burst of leads is not lost.

Why does data get overwritten or duplicated in a sheet?

A sheet has no transactions, so two processes can overwrite each other, and updating by row number breaks after sorting. Unique record IDs, appending instead of editing, and protection against redelivered events help.

When should I move from a spreadsheet to a database?

When you hit quotas, see lost or duplicated records, or need role-based access or links between data. A gradual move works well: the database becomes the source of truth and the sheet stays for reports.

Related service

CRM, ERP and API integrations built for your workflows

When teams copy data between systems by hand, delays and mistakes become part of the process. We automate the exchange and make its status visible to the people running it.

Learn about the service
Other articles
Contact

Shall we discuss your task?

Thirty minutes on a call — and you understand the architecture, timeline and engagement format. No obligations.

Or message us on Telegram →Follow our Telegram channel →

Enter your Telegram or email so we can reply.

We reply within 15 minutes.