Refresh Token Dropbox Expired

[Daniel_StrmCtrl]

Describe the problem/error/question

I’m facing an issue where the refresh token of Dropbox gets expired and I’ve got no idea how to refresh it automaticly.

I’ve followed this topics but with these the toke expires still after a while:

Dropbox API token expiration

Question Dropbox only allows shortlived API tockens (4 hours according to their article). And they say you need to use refresh tokens to use it without manually refreshong tokens. How to deal with expiring tokens in n8n? Right now I want to make automatic backups of my workflow daily, but that’s impossible for me without going and manually refreshing the token. But it’s more general qusetion, I just want n8n has continious access to my dropbox. Is that even possible for me to figure out if I’…

No Refresh Token - Dropbox

Describe the problem/error/question I created Generic Credentials for DropBox using another thread I found on the community page and configured the credentials for Oauth 2 for Dropbox. However, I am still receiving errors for “no refresh token” after a certain period of time. The only thing that solves this, is manually refreshing the connection in N8N which is obviously not ideal. I am looking for help solving this, as I am not super technically savvy when it comes to authentication and tokeniz…

What is the error message (if any)?

Please share your workflow

It stops at the “Share Folders Dropbox”

Information on your n8n setup

• n8n version: 1.85.4 (Self Hosted)
• Running n8n via (selfhosted Railway):

[barn4k]

hello @Daniel_StrmCtrl

Your second HTTP node has two Headers sections (one defined in the oAuth2Api credentials and another one in the node’s headers). I can’t say which one would be used, but that may be the root cause. I suppose the node’s header will have precedence over the headers.

Why you are not using the default OAuth2.0 credentials or the dropbox node (which uses the default OAuth 2.0 with predefined scopes)?

[Daniel_StrmCtrl]

I disabled the one in the node and did a rerun. Sadly problem persists.

Reason I’m not using the Dropbox node is because it doesn’t have the sharing ability ( only has a few scopes ). I have to revert to the http one to do that. Unless I’m missing something.

[Daniel_StrmCtrl]

Bumping it up as I still didn’t find a solution.

[Daniel_StrmCtrl]

Last final bump - Still need help with this and haven’t found solution on my own.

[barn4k]

What I can advice is to generate the new access token each time you are accessing the dropbox. In that case you won’t need the refresh token.

Steps would be:

1. make a request to the /oauth2/authorize endpoint to get the auth code
2. make a request to the /oauth2/token endpoint with that code to get the access token
3. make a request to the desired API endpoint with the token from the 2nd step.

Otherwise, you will need to set another workflow to automatically refresh tokens (e.g. once a day)

See Dropbox OAuth Guide - Dropbox (“Using Refresh Tokens” Section)