Can anyone explain to me how the Add Rows function works (linking to a google sheet) in terms of how it puts them in, I can see it is 1 at a time but is that 1 at a time per individual sheet or per workbook or just for my account it will only run 1 at a time? (I have lots of different tables exporting to workbooks for cleaning and processing and wondering if it will move faster if I split up the sheets into seperate workbooks)
The Add Rows function in Clay adds one row at a time to a specified Google Sheet. It works on a per-sheet basis, not per workbook or account. Splitting sheets into separate workbooks won't affect the speed of the Add Rows function. Can you clarify what specific performance improvements you're looking to achieve with your data export process?
I'm just watching as it has all of my rows queued up to add and it seems to be running one row at a time per workbook
The Add Rows function adds one row at a time to a Google Sheet. The sources don't specify whether this is per sheet, per workbook, or per account, but based on your observation that it appears to run one row at a time per workbook, that seems to be the current behavior. Splitting sheets into separate workbooks likely won't improve speed since the Add Rows function processes sequentially regardless of the workbook structure.
I was thinking if I had different tables loading into different workbooks, would that be faster or is it all just in one looooongg queue for the sheets api?
Splitting tables into different Google workbooks won't make the Add Rows function run faster. Clay processes Add Rows actions sequentially, one row at a time, regardless of workbook structure. Can you share more about the size of your tables and the specific performance issues you're experiencing?