• Custom n8n node
  • Microsoft 365
  • AI-agent tool

SharePoint

Manage SharePoint document libraries (list, upload, download, move, copy, delete) through Microsoft Graph.

How it works in practice

Documents filed in SharePoint, where people look

How we apply it

In our robots for a Bulgarian accounting firm, SharePoint is where scanned batches come in and where statements, invoices and run reports are filed, per company and per period.

This node reads and writes SharePoint (and OneDrive for Business) document libraries through the Microsoft Graph API. Beyond basic transfer it lists a whole library recursively using Graph's delta endpoint with content hashes, copies and moves folders with polling of the asynchronous Graph job, and handles name conflicts by replacing, failing or renaming. Site and drive pickers support search as you type, and paging through @odata.nextLink is automatic.

The stock nodes stop short of the folder-level work that real SharePoint archives need, so we wrote it: copy and move whole folder trees, upload with explicit conflict behaviour, and a recursive listing with quickXorHash hashes that lets a workflow detect which files changed. You can authenticate with an n8n OAuth2 credential, or paste an access token as a node parameter.

It reaches further than any other node of ours, in 60 production workflows: archiving processed invoices and statements into per-customer folders, fetching new documents from a shared library to feed Document AI, and publishing generated reports to a site for business users.

Limits: it covers drives, files and folders only. SharePoint lists and site search are not supported, whatever older documentation may suggest. Delete sends items to the SharePoint recycle bin, and a copy job is polled for up to 60 seconds.

For your technical team: it installs from npm as

n8n-nodes-kt-sharepoint

What it means for you

  • No manual filing or renaming

  • Staff keep working in the SharePoint they already know

  • Name clashes are settled by clear rules, not by accident

Want SharePoint in your n8n?

Tell us what the workflow has to do and what it connects to. We will say whether this node covers it as it stands, what we would add, and when a different approach is the better one.