Storing OAuth2.0 Access token to reference until expired between workflow runs

Questions
1

I am trying to set up a custom OAuth2 Client Credentials flow in n8n to manage access and refresh tokens. My goal is to store the access token for reuse between workflow runs until it expires. When a request fails due to token expiration, I want to use an HTTP node to obtain a new access token, using the refresh token, store this new access token, and then retry the request.

But how can I save the access token so it can be reused between workflow runs until expired and then updated using a fresh token node.?

I am self-hosting on Linux VPS in docker container using Coolify.

Information on your n8n setup

  • n8n version: 1.53.2
  • Database (default): Postgres
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • Operating system: Linux
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

@DaviG , have you considered utilizing static data, getWorkflowStaticData | n8n Docs?

1 Like
4

B̶u̶t̶ d̶o̶e̶s̶ t̶h̶i̶s̶ s̶t̶a̶t̶i̶c̶ d̶a̶t̶a̶ s̶u̶r̶v̶i̶v̶e̶ b̶e̶t̶w̶e̶e̶n̶ w̶o̶r̶k̶f̶l̶o̶w̶ t̶r̶i̶g̶g̶e̶r̶s̶, o̶r̶ i̶s̶ i̶t̶ o̶n̶l̶y̶ a̶l̶i̶v̶e̶ d̶u̶r̶i̶n̶g̶ t̶h̶e̶ e̶a̶c̶h̶ w̶o̶r̶k̶f̶l̶o̶w̶ e̶x̶e̶c̶u̶t̶i̶o̶n̶ t̶h̶e̶n̶ d̶e̶s̶t̶r̶o̶y̶i̶n̶g̶ t̶h̶a̶t̶ s̶t̶a̶t̶i̶c̶ d̶a̶t̶a̶?̶

Tested in with a live webhook, seems to work as intended, but is there any situation that would lead to this static data being cleared?

5

@DaviG , the whole idea behind the “static data” (as the name suggests) is to persist between the workflow executions. I can only add that the static data won’t be saved between executions unless you:

  1. are using an automatic trigger node (such as schedule or webhook)
    and
  2. have activated the workflow

Also, be aware that it gets saved after the execution is finished. So it will only be accessible for executions that started after the previous one is done.

I do not know for sure but expect the data to be stored in the database to fulfill its purpose.

1 Like
6

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.