To close out this thread, I wanted to clarify how file uploads to SharePoint work using the Celigo SharePoint connector.
The connector does support uploading files, but it does not aggregate records into a file. That means if your use case requires compiling multiple records into a single file (like a CSV or JSON file), you’ll need a separate flow to handle that aggregation step using another file provider — such as Google Drive, the NetSuite File Cabinet, FTP, S3, etc.
Then, you can build a second flow to move the generated file from that source into SharePoint.
Example: Moving NetSuite Files to SharePoint
Below is a flow example that takes files from NetSuite and uploads them to a folder in SharePoint.
- The flow allows you to select the SharePoint site, then the drive, and then specify the folder path to upload into.
- The only field you may need to change is
{{{record.file_name}}}— update this to whatever filename you want (including the file extension). - You may also need to adjust the
blobKeypath if your file structure is different.
Download the flow template (7 KB)
