Why can't RowFold save into my existing Google Drive folder?
RowFold asks Google for access only to the files and folders it creates, not to your whole Drive. That keeps the rest of your Drive out of its reach, and it also puts a folder you made yourself out of bounds. Create the folders from RowFold instead, with one Create a Google Drive folder step per client or job and the new folder's id saved on the record.
How big a file can I save?
Up to 5 MB to Google Drive and 25 MB to OneDrive. A larger file fails the step with a message naming the limit, and nothing is uploaded. Most PDFs and phone photos fit. Long videos and large drawings are better kept in the drive directly, with a link to them stored on the record, where the grid can open them.
Which file does it send when a record has several?
The newest one. That means the file added last to the Attachment field you chose, which is usually the file a step earlier in the same run has just made, such as the PDF from Generate a PDF. If the field is empty, the step fails and says which record had no file, so a missing document never goes unnoticed.
Can the folder depend on the record?
Yes. On OneDrive, the Folder box takes a path with tokens, such as Clients/{{record.client}}/Invoices, up to six folders deep, and RowFold creates whatever is missing. On Google Drive, keep each client's folder id in a field and use that field's token in Destination folder ID, reaching through a link to the client if the file is on another table.
Can it save to a shared drive or a SharePoint site?
Not directly. The OneDrive step saves into the connected account's own OneDrive, and the Google Drive step into My Drive or a folder RowFold made. To share the files, share the parent folder once from the drive. Every file RowFold saves into it afterwards is shared the same way, with no step needed per file.