How to Automatically Upload Files to a SharePoint Document Library
Question details
The user needs to automate the process of uploading daily bid-result files from a designated folder to a SharePoint document library.

- Product
- SharePoint
- Device & OS
- not provided
- Scenario
- Setting up a workflow to automatically transfer newly created daily files into a specific SharePoint repository to eliminate manual uploads.
- Observed behavior
- The file upload process is currently manual, and the user is looking to establish an automated workflow utilizing Microsoft Power Automate.
Ensure you have Edit or Contribute permissions for the target SharePoint document library and an active Microsoft Power Automate account before configuring the workflow.
Use Power Automate with Cloud Storage (OneDrive/SharePoint)
Create an automated cloud flow that triggers whenever a new file is added to a designated cloud folder, automatically copying it to SharePoint.
This is the most seamless method, utilizing standard Power Automate connectors. By syncing your local designated folder to OneDrive, Power Automate can detect new files instantly and push them to SharePoint without requiring premium gateways.
Log into Microsoft Power Automate. On the left sidebar, click 'Create' and select 'Automated cloud flow'.
Name your flow and search for the trigger 'When a file is created'. Select the one corresponding to your source folder (e.g., OneDrive for Business), and click 'Create'. Specify the exact folder path where your daily bid-result files are saved.
Click 'New step' and search for 'SharePoint - Create file'. Select it from the list of actions.
Select your target SharePoint 'Site Address' and 'Folder Path'. Click inside the 'File Name' field and select 'File Name' from the dynamic content menu. Do the same for 'File Content', ensuring it pulls from the trigger step.
Click 'Save' at the top or bottom of the screen. Drop a test file into your source folder and verify that it automatically appears in your SharePoint document library.

Use Power Automate Desktop for Local Network Drives
Use this solution if your files are stored on a local on-premises server or drive that cannot be synced to a cloud service like OneDrive.
Create and Edit Daily Reports Seamlessly with WPS Office
While Microsoft Power Automate handles your SharePoint automation, WPS Office provides a free, lightweight, and highly compatible suite for creating and editing your daily bid-result files. Enjoy a familiar interface and seamless document management without heavy subscription fees.
- 1. Download the Installer: Visit the official WPS Office website and download the free version for your operating system.
- 2. Install the Software: Run the installer file and follow the on-screen prompts to complete the setup.
- 3. Edit Your Documents: Open your bid-result spreadsheets or documents directly in WPS Office with complete formatting retention.

Frequently Asked Questions
Do I need a premium license to upload local files to SharePoint using Power Automate?
Yes, connecting directly to a local file system using the On-premises data gateway typically requires a premium Power Automate license. A free workaround is to sync your local folder with OneDrive and use the standard OneDrive trigger.
What happens if a file with the same name already exists in the SharePoint library?
By default, the 'Create file' action may fail if a file with the identical name already exists. You can adjust the flow to either overwrite the existing file or append a dynamic timestamp to the file name to ensure every upload is unique.
Can I schedule the file upload to happen at a specific time every day?
Yes. Instead of using the 'When a file is created' trigger, you can use the 'Recurrence' schedule trigger to run at a specific time daily. You would then add actions to 'List files in folder', filter for new files, and iterate through them using 'Apply to each' to upload them to SharePoint.
How do I troubleshoot if my SharePoint upload flow keeps failing?
Go to the 'My flows' section in Power Automate, click on your flow, and check the '28-day run history'. Clicking on a failed run will display exact error messages on the specific step that broke, such as missing permissions or invalid folder paths.




