Describe the problem/error/question
Hi !
I’m struggling with the Sharepoint node. I seem to have a problem on the token refresh part.
When running the node on a schedule trigger, my workflow fails after the first access token has gone out of date.
I’ve already set up other Microsoft oAuth types of credentials for other worflows, which are refreshing tokens with no problem.
I have 1 excel online, 1 onedrive, a few outlook, all working well so I guess, I’ve setup the credentials as it should be : I’ve used the same settings on all.
My app registration do have the offline_access enabled for Microsoft Graph, and I can’t find a specific “offline access” grant in the Sharepoint list.
If someone could help me with how to find where I’ve messed up, it would be very nice 
What is the error message (if any)?
Authorization failed - please check your credentials
The access token has expired. It’s valid from ‘6/6/2025 4:40:09 AM’ and to ‘6/6/2025 6:02:23 AM’.
My Workflow
Share the output returned by the last node
It’s the first node after the schedule trigger.
Information on your n8n setup
- n8n version: 1.95.3
- Database (default: SQLite): SQLlite
- n8n EXECUTIONS_PROCESS setting: default
- Running n8n via : Docker (thru Portainer)
- Operating system: Linux Alpine
4 Likes
I’m experiencing the same issue with the SharePoint node in n8n—tokens don’t refresh after expiration, even though other Microsoft OAuth credentials (OneDrive, Outlook, Excel Online) work fine with auto-refresh.
- Access token works initially but fails after expiry
- Error: “Authorization failed - please check your credentials. The access token has expired…”
It seems like the SharePoint node doesn’t properly handle the refresh token flow, even though it’s granted.
Would really appreciate if anyone has found a fix or workaround for this—especially if there’s a known issue or extra config needed specifically for SharePoint.
Having the same issue as well. I have tried granting a whole bunch of different permissions. I have tried adding both delegated and application permissions depending on if it is using Client credentials or Authoriszation Code grant type under the hood. Neither work.
Also, in the docs it would be nice to have a table the shows which scopes are needed for which of the sharepoint node actions. This would make configuring much easier.
1 Like
Looks like an issue has been created in github but not yet reviewed and with no PR against it. My guess is it will still be a month a minimum until we see a patch for latest non-prerelease version.
Microsoft SharePoint Node - Access token has expired · Issue #16070 · n8n-io/n8n
Having the same issue.