Field Notes: SharePoint Folders That Create Themselves

A short one. Someone asked how the folder-creation piece works, so here it is end to end.

The trigger

A HubSpot workflow fires on deal stage change — in our case entering "Won", though "Contract Sent" is the more common choice because people want the folder before they need it. The workflow calls a webhook with the deal ID.

The build

The webhook lands in n8n, which does four things in order:

1. Fetch the deal from HubSpot to get the company name, deal name, and close date. Don't trust the webhook payload to carry everything; fetch fresh.
2. Build the folder name from record fields — we use CompanyName - DealName with characters SharePoint rejects stripped. Never let a human type this; the whole point is that the name is predictable.
3. Create the folder tree via Microsoft Graph, from a template structure. Same subfolders every time.
4. Write the folder URL back onto the HubSpot deal as a property, so the link is on the record rather than in somebody's bookmarks.

That last step is what makes people actually use it.

The permission mistake

Here's the part worth the post.

The obvious way to build this is with an app registration holding Sites.ReadWrite.All. It works immediately, and it means your automation can write to every SharePoint site in the tenant — including HR and Finance.

Nothing about the folder feature requires that. Use Sites.Selected instead, then grant the app write access to the one document library it needs. It's more setup and one more conversation with whoever owns the tenant, and it means a bug in your workflow can't reach payroll.

We've seen the broad-permission version in the wild more than once, usually because a tutorial used it. If you inherit one of these, that's the first thing to change.

What it doesn't do

It doesn't move existing documents, and it doesn't reorganize a library that's already a mess. Creating structure going forward is a different job from cleaning up what's there — if you need both, do the cleanup as its own project first, or you'll have two conventions living side by side.

More detail on the SharePoint automation page, and the extraction side is on document automation.