Go High level Oauth2.0 Refresh token issue

Questions
,
1

It seems the refresh token is getting expired immediately after using once, and the api to refresh access token must be called atleast 8 seconds after on refresh or else it would return the invalid token error

This is the error im receving

{
    "error": "invalid_grant",
    "error_description": "This refresh token is invalid"
}

Im using the “https://services.leadconnectorhq.com/oauth/token” api to refresh my access token. This used to work fine till yesterday

2

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
3

Hey @Milan_K_Jain,

Welcome to the community :raised_hands:

Did you update n8n before it stopped working or did it just stop working? Are you also using our node and credential or a generic oauth credential?

4

Running into same issue. Refresh Token is expiring after 1 use. Everything worked fine up until last week or so. Refresh Token should be good up to 1 year per their documentation.

5

I am having the same issue. I keep needing to reconnect the credential to get it to work.

6

The highlevel node really needs to and the private integrations method (api key per sub-location) and remove the Oauth or keep both so can choose.

Private integrations is a much easier auth method similar to the old v1 API with api keys

7

Same issue for me !