Google Sheets
Last updated
Was this helpful?
Last updated
Was this helpful?
You can add a Google Sheet for your TaskBot to pull data from, update it or append new data to it.
Yes. Simply add new columns directly in your Google Sheet, and then click on Refetch columns from Google Sheet on your TaskBot page, as shown here: .
If you change column names or delete some of the columns in your Google Sheet, those table references that refer to them in your building blocks will no longer be valid. If you click on Refetch columns from Google Sheet, the columns that are no longer present in your Google Sheet will be removed automatically from all the building block references. If you rename or delete columns that are not referenced in any of your building blocks, then nothing happens and no action is needed.
Column matching is not case-sensitive. This means that if you change the case of your column names in your Google Sheet (for example, from "column one" to "Column One"), this will have no impact on your references.
To avoid hitting Google Sheets usage limits, your TaskBot processes rows in batches — by default, it saves updates every 50 rows.
For example, if your sheet has 500 rows and your TaskBot loops through each one, it will update the sheet 10 times during the run (once after every 50 rows). This significantly reduces the chance of triggering quota errors.
You can adjust this batch size in the Additional options of the Start Repeat building block — for example, set it to 1 if you want the TaskBot to save data after every row.
If a usage limit is exceeded during a TaskBot run, the TaskBot will retry several times automatically. If Google Sheets continues to return a rate limit error after multiple attempts, the TaskBot will stop and you’ll see an error message in your Run Reports (see Using Run Reports). Usage limits are most likely to occur when you run multiple TaskBots in parallel that all use Google Sheets.
Official Google Sheets documentation page on usage limits: .
Your TaskBot will check if the Google Sheet link is valid at the start of its run. If it's not valid or your authentication session has expired, it will not proceed with the run and you will see an error message in your Run Reports.
See Convert Native Table to a Google Sheet.
Let's go over an example.
You have TaskBot A with table id 123 pointing to Google Sheet A.
Then you duplicate your TaskBot A. Now TaskBot B is created with a different table id 456 still pointing to Google Sheet A.
The Google Sheet is not re-created in your Google Drive. Both tables point to the same Sheet.
Now you might want to do either of the two:
Keep the new TaskBot B’s table as it is. It will update/use data in the same sheet as TaskBot A.
Link TaskBot B to a different sheet. You can simply click on "Edit Google Sheet link" and add a new Google Sheet in your TaskBot B without having to re-map any of the table references in your building blocks. That's because the reference used is only the table id, the column names do not need to be re-mapped (unless the column names in your other Sheet are different and do not match to the column name references in the building blocks).
If you need to re-authenticate to your Google Sheets, you need to first remove its connection from your Google Account.
Go to your Google account settings, click on Data & Privacy, scroll down to Data from apps and services you use, select Third-party apps and services and find ZeroWork in that list. Once you click on ZeroWork, scroll down to the option called Delete all connections you have with ZeroWork. Now you can re-authenticate your connection to Google Sheets.