Dropbox Outh2 API shareable url with scope sharing.wrtire question

[Blueli]

Hello

I realized the built-in dropbox outh2 API has only 4 scopes.

Without sharing.write we are not able to create shareable URL from Dropbox. I followed this thread to create a custom Generic Credential Type

Drop box Share URL

Hi @Keep_Innovations , very strange! I typically use gdrive not dropbox, so not sure what could be going on. And feel free to request the feature in the Feature Request forum. If enough people vote for the feature, they will add it.

I managed to create one, add the necessary scope, and it worked for a while.
Later I found that the HTTP quest for dropbox shareable URL only output error

I did not know what happened But after I click the reconnect button, the flow works again.

Is it normal that we have to reconnect the Dropbox OAuth2 from time to time? I need to avoid this situation because I don’t know how often I will have to reconnect.
This is their document, but I have no knowledge about OAuth2, so I cannot find if my question is answered there.

Dropbox OAuth Guide

Appreciate for your help
Thanks

[n8n]

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:

[barn4k]

hello @Blueli

Am I right, that you are not using the Credentials, but passing the token directly via the Edit Fields node?

[Blueli]

Yes, I set both. Credential and the token on my HTTP node,
Should I remove that Authorization header with the token? But if I do that, it will not work. How should I do it correctly?

Thanks

[barn4k]

if you are setting the Authorization header via the Send Headers property, then your Credentials from Authentication section won’t work and will be overwritten (or vice versa, didn’t check it, but the both uses the same field).

The proper way is to set the Authorization with your OAuth 2.0 with custom scope via Credentials and disable the Send headers option. Otherwise you’ll need to re-obtain the token every X days (depending on the Dropbox API)

[Blueli]

Hello
//The proper way is to set the Authorization with your OAuth 2.0 with custom scope via Credentials

Would you please elaborate more? I have already set Credentials here, am I not doing it correct?

Thanks

[Blueli]

It seems that I have entered the incorrect access token URL.
It should be
https://api.dropboxapi.com/oauth2/token

I will wait and see if the problem remains tomorrow.

[barn4k]

You have set it correctly. But you don’t need to provide the Authorization Header in the HTTP node.

That part is handled by the Credentials you have created before.