I’ve submitted a PR that enhances the SharePoint node by allowing users to select document libraries other than the default “Documents” library. I tested this thoroughly on my local n8n instance and confirmed that it works as expected.
What is the expected timeline for reviewing and merging this PR into a release? This limitation in the SharePoint node is a significant blocker for many enterprise and security‑conscious use cases, where organisations often configure additional document libraries with distinct IAM settings rather than relying solely on the default Documents library.
Would i be better off creating a separate community node and instruct my enterprise users to use that instead of the core n8n SharePoint node?
master ← elabbarw:Feature/Sharepoint-All-Folders
opened 12:49PM - 27 Jan 26 UTC
## Summary
This PR adds support for selecting document libraries (drives) in … the Microsoft SharePoint node, enabling users to work with files across all document libraries on a SharePoint site, not just the default "Documents" library.
### Changes
- **New Document Library selector**: Added a `driveRLC` resource locator control that allows users to select any document library on a SharePoint site
- **Updated file operations**: Download, Upload, and Update operations now include the Document Library field
- **New `getDrives` list search method**: Enumerates all document libraries by querying site lists and checking which ones have associated drives
- **Modified API endpoints**: Updated all file operation URLs from `/sites/{site}/drive/...` to `/sites/{site}/drives/{drive}/...`
- **Root folder option**: Added "/ (Library root)" option in folder selection for uploading/downloading from the library root
- **Updated tests**: Added test coverage for the new `getDrives` functionality and updated existing tests for `drive` parameter
### How it works
The `getDrives` method fetches all lists from the SharePoint site, then checks each non-hidden list to see if it has an associated drive (which indicates it's a document library). This approach works with custom folder structures and sites that don't have a default "Documents" library.
### How to test
1. Connect to a SharePoint site that has multiple document libraries (or one without a default "Documents" folder)
2. Select the **File** resource and any operation (Download, Upload, Update)
3. Select a Site - the Document Library dropdown should now appear
4. Verify all document libraries on the site are listed
5. Select a library, then select a folder and file
6. Execute the operation and verify it works correctly
## Review / Merge checklist
- [x] PR title and summary are descriptive. ([conventions](../blob/master/.github/pull_request_title_conventions.md))
- [ ] [Docs updated](https://github.com/n8n-io/n8n-docs) or follow-up ticket created.
- [x] Tests included.
- [ ] PR Labeled with `release/backport` (if the PR is an urgent fix that needs to be backported)
wow…. community node it is…