N8N not refreshing Oauth token in graphql node

Questions
,
1

I am using the Pipefy API with a service account, which is an Oauth2 authentication . This authentication works until the token expires. When the token expires using the graphql node it does not update the token:

image
image1464×827 33 KB

The API correctly returns the code 401 when an expired token is sent, the same query (with the same expired token) in the postman

image
image1491×501 30.6 KB

Information on your n8n setup

  • n8nVersion: 1.58.2
  • platform: docker (self-hosted)
  • nodeJsVersion: 20.15.0
  • database: postgres
  • executionMode: regular
  • license: community
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

Adding one more information…

In the normal HTTP node, authentication works and the token is renewed, this behavior only happens in the graphql node.

image
image1310×973 30.6 KB

5

Hi @Luan,

This sounds like a bug in the GraphQL node, thanks for bringing this to our attention. Will investigate this internally and keep you posted :slight_smile: Tracking [NODE-1766]

7

Hey @aya, any updates on this issue?

I can confirm that the problem continues in version:

core

  • n8nVersion: 1.69.2
  • platform: docker (self-hosted)
  • nodeJsVersion: 20.18.0
  • database: postgres
  • executionMode: regular
  • license: community
8

Hi @Luan,

No updates yet unfortunately :frowning: I’ll ping internally to see if we can bump this up. In the meantime, I recommend that you use the HTTP request node instead.

9

Hi @aya , still no updates? This is an important stopper for us :frowning:

10

Hi @pitazzo, we don’t have an ETA for this yet unfortunately :cry: You should be able to use the HTTP Request node instead in the meantime. We’ll update this as soon as we have any updates :slight_smile:

11

@pitazzo I followed Aya’s tip and am using normal http node, like this: