Problems getting Workbooks via Excel node

Describe the problem/error/question:

My Excel node seems to have stopped pulling anything from my account.

What is the error message (if any)?:

No messages, basically just nothing found. The workflow completes successfully. But there are no workbooks coming up.

Information on your n8n setup

  • n8n version: 1.59.4
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • **Running n8n via (Docker, npm, n8n cloud, desktop app): Proxmox, npm, VE Helper Scripts

Redid all my API keys.

Using OneDrive node, I can see folders and contents.
Using Excel Node, It will not return ANY values at all. No matter what.

Doing a HTTP request Node it return with 200 and OK.

But value says: empty arrays

Hi @rosk,

In the HTTP request the status is 200 but it also didn’t return any files. So much like the Excel node, there is no error but also no output.

Are you also having this issue with other actions in the Excel node?

Yeah, I know. I don’t get anything when using the Excel node. But If I use OneDrive node I get folders and files.
With OneDrive node I can make new folder and stuff.

But using Excel node I get nothing. None of the files I have in my OneDrive shows up using the Excel node.

Here I’m just asking for the contents within a folder with OneDrive node. But trying to look for workbooks with the Excel node it comes back with nothing.

Am I doing something wrong? has something changed? As I had no problem pulling up workbooks before.

Something strange going on here.

I have an old workflow with an Excel node in it. If I try to run it, it works! It pulls the data.

But if I try to set up a new identical function, it’s not possible. Searching for the exact same workbook returns nothing. :joy:

Small update, I have opened a support ticket with Microsoft, and they are looking into it.

Thank you for providing information in your response. We appreciate your efforts.

We wanted to inform you that we have escalated your case to our engineering team for further investigation.

They will be looking into the issue, and we will keep you updated on the progress.

Hopefully, they find something.

PS: I also tried setting up a fresh installment of n8n locally, with a new set of credentials. No joy.