HubSpot OAuth “Missing Scopes” Error in n8n (Scopes Already Added in Public App)

Questions
1

Hi everyone,

I am facing an issue while connecting HubSpot with n8n using OAuth2 credentials.

Issue Description

I created a Public App in HubSpot and added all the required scopes there. However, when I try to connect HubSpot in n8n (by selecting HubSpot OAuth2 and entering the Client ID and Client Secret), after selecting the account, I receive a “missing scopes” error.

The issue is that the scopes mentioned in the error are already added in my HubSpot Public App settings.

What I Have Tried

  • Created a new Public App in HubSpot

  • Added all required scopes

  • Re-checked and confirmed scopes are enabled

  • Reconnected multiple times

  • Regenerated Client Secret

  • Tried different methods and configurations

Despite trying all possible methods, HubSpot is still not connecting with n8n and I keep getting the same missing scopes error.

Questions

  • Does n8n require specific scopes different from HubSpot’s standard scopes?

  • Do I need to reauthorize the app after updating scopes?

  • Is there any additional configuration required in n8n?

  • Could this be a redirect URL issue?

If anyone has faced this issue before, please guide me on how to resolve it.

You can also contact me on WhatsApp if needed:
+923424332577

Thanks in advance

2

Hi @ali_awais

hubspot’s oauth chokes on scope mismatches constantly. super annoying.

the scopes you set in the hubspot dev portal have to perfectly match whatever is requested inside your n8n credential setup. if n8n asks for a scope you didn’t check in hubspot (or the other way around) the whole thing just nopes out.

and yes… you absolutely have to reauthorize after changing scopes. hubspot caches token grants aggressively. best bet is to delete the credential entirely in n8n, open an incognito window, and build a brand new credential from scratch.

also worth checking your n8n version — older versions sometimes request legacy hubspot scopes that hubspot recently killed off.

try the incognito rebuild first. usually sorts it out.

3

hey, this is a known quirk where n8n’s OAuth URL doesn’t actually update when you add scopes to your HubSpot app after the fact. When you hit the connect button, check the URL in your browser and compare the scope= parameter against what HubSpot shows in your app’s Install URL section, they probably don’t match. You’ll need to manually swap in the correct scopes from HubSpot’s install URL to get it to work.