Google Sheets to SQL Sync
Keep your SQL database in sync with Google Sheets using googlesheets-sql-sync.
Let users manually insert data using Google Sheets while having the power of all available SQL tooling for further processing.
googlesheets-sql-sync uses JDBC and bundles the PostgreSQL driver. Additional drivers can be added any time. If you would like to add support for SQLite, MySQL or any other SQL database, open an issue and it can probably be added in no time.
Assumptions and simplifications
To simplify the task of synchronisation, the following assumptions are made:
- Sync happens not too frequently. Think minutes, not milliseconds.
- Number of tables to sync is not too high. Maybe a hundred but not a million.
- The Google Sheets are not too big. They might contain a thousand rows but not millions.
- Headers are mostly stable. It is an exception to rename, add or delete columns.
This allows for a few simplifications in the implementation:
- Do all specified sync tasks in sequence. There is enough time for this.
- Limit API requests to Google's API to one a second to prevent rate limits as much as possible.
- Truncate each table on every sync to ensure all changes are applied.
- Log error when table schema doesn't match headers from sheet and require the user to check error manually. Most likely the user simply drops the table in this case and moves on.
- Re-read the config file from disk before each sync interval, which allows for adjusting the config while the system is running.
- Make sure you have Java 8+ installed. Check by running
- Download latest
Setup Google Application
- Create a new Project or work in an existing one
- Enable the Sheets API
- Setup your app's OAuth consent screen
If this is an organisation-internal service, you most likely want to set it as internal and select the scope
- Create a new OAuth client ID or use an existing one
- Set "Application type" to "Web application"
- Set at least one correct "Authorized redirect URI". To run googlesheets-sql-sync on your local machine with default settings use http://localhost:9955/oauth
- Keep "Client ID" and "Client secret" handy for later
- Create an empty config file
java -jar googlesheets-sql-sync.jar --init
Now fill out the missing information in the config file.
Use your Google credentials from above.
Specify at least one target and one sheet using that target.
You can find more DB options in the JDBC docs.
tableas you wish for it to appear in your database.
To get a
spreadsheet_id, open one of your Google Sheets and copy the part between
/editfrom the URL bar in your Browser.
A1:Z10. Skip the number to select all rows - like
A:ZZ. You can also specify a sheet if your spreadsheet contains multiple sheets by prefixing th range like
SomeSheet!A:ZZ. For example, the
Start the program with:
java -jar googlesheets-sql-sync.jar
You will be prompted to visit an OAuth URL to authorize and connect your Google Account.
After successful authorization, a first sync is triggered and further ones will occur in the specified interval.
Running without Server
Often you don't want to open up another port just for OAuth of a small sync tool.
To work around this you can run
java -jar googlesheets-sql-sync.jar --auth-only on your local machine, then copy the generated
googlesheets_sql_sync.auth.json file to your server and on the server run
java -jar googlesheets-sql-sync.jar --no-server
The program can be configured using command line flags. To see available options, run:
java -jar googlesheets-sql-sync.jar --help
- When you authenticate a Google OAuth app, then throw away your
.auth.jsonfile and try to re-authenticate, Google for some reason will only send you
refresh_token. To fix this go to https://myaccount.google.com/permissions remove the app's permission and try again.
Let me know if you run into any issues or if you have any suggestions for improvements.
Use as Clojure package
- You can generate a config file with
- Generate and validate options for running the system with
- Run the system with
#googlesheets-sql-sync.log/errorto modify or disable logging.
- Make sure you have Leinigen installed.
lein testRun tests
lein runRun the whole system
lein replStart in dev mode with REPL enabled
- Try out comments in dev namespace
Building for production