N8N OAuth 2 is the biggest disaster I’m experiencing at the moment.
Instead of constantly adding new features, how about making the existing features useful so that they actually work?
First of all:
No, I’m not a n8n beginner who doesn’t know what he’s doing, at least not in my field of work. I use the custom n8n’s oauth2 api a lot because the standard ones have far too few functions and I have to do a lot of customization.
For example: I work a lot with Microsoft Teams Graph Api. I created my credentials for this and am completely dependent on them. Now, I have everything set up correctly and the workflow is working perfectly. But the next day, I get the message “no credentials were sent in the request.” Then I just wait 5-10 minutes and run the node several times, and then it magically works again. But since it didn’t work at the beginning because the refresh token wasn’t automatically updated correctly, the workflow stopped, which is very critical for me. I have workflows where I work with custom HTTPS nodes for more than half of the nodes, and I can’t insert an if loop everywhere to execute it again. No, that’s not possible. And the retry on fail function is completely useless. You can only set it to 5 seconds and a maximum of 5 times. That has never worked. If you could set it to 5 minutes and up to 5 times, that would be a different story. But it will never come to that.
Why doesn’t it work with n8n?
And no, it’s not because I configured something wrong. I’ve already tried other workflows, even a completely different n8n account, and it works every time, but the refresh token isn’t always updated correctly. This is a critical internal n8n error. I request a timely fix. As you can see, this problem has existed for several years and has not been resolved. This is unacceptable!