How can I fix this issue.
Hey, this specific 403 from Inoreader is almost always tied to how the OAuth flow is set up. I’ve fixed this exact issue before, and it usually comes down to one of three things: the redirect URL isn’t matching n8n’s callback exactly, the scopes don’t align with what the node is trying to access, or the token needs to be regenerated. If you share your credential setup (no keys needed), I can pinpoint the exact misconfiguration and guide you straight to the fix.
Thanks for the response, Could you share me a guide on how you have setup the node?
@Zulu_Ttk if you could share any docs or guidence it would be helpful for me.
@Zulu_Ttk Anyone who works with inoreader in n8n experiences this issue. You install the inoreader node (1.0.5) then create the Inoreader credential, filling in the form with the content from the inoreader dev console. Scopes are exactly as documented: “read write”. ID and Secret are exactly as shown in the dev console. do the connection and that works. You can now run your workflow a number of times within 24 hours and all will work, but it will not renew.