Has anyone successfully connected Dropbox’s API with Bubble’s API Connector?
When trying to authenticate using an OAuth2 User-Agent Flow, I get the following error:
Now, for anyone who hasn’t worked with Dropbox’s API, they do have one unique characteristic where they seem to use POST where you might otherwise expect a GET. Although, I’m hoping that’s not the problem here.
This is my current setup in the Bubble API Connector:
Honestly, I’m only using OAuth because DropBox doesn’t seem to supply long-lived tokens anymore. I don’t need users to access their DropBox accounts, this is all only for personal use and will only use my account. So, if anyone knows how to generate a long-lived token that would be great too. I’ve gotten all my calls to work with short-lived API tokens generated from my DropBox App Console. Just wish they’d let me generate a long-lived token.
Instead, I used Make to handle all my Dropbox calls and I just setup webhooks to keep all the functionality I needed within Dropbox.
You could use Zapier or any other API product as well, Make is just much cheaper and has performed very well for me with high volumes as a middle-man in cases like this.
This is obviously much less efficient, but it works. I’d love for someone to figure out Dropbox authentication within Bubble though.
Interesting. I think I like your implementation better than mine, as it’s cleaner and keeps more actions contained within Bubble.
In addition, polling a key every three hours probably isn’t as resource heavy as my more complex “on-demand” method… as long as you have enough traffic to supersede the poll anyway.
Hello I want to implement this solution that has worked for you… Can you or someone help me understand how the outer API configuration should look like? Mine looks like the screenshot, but I am getting an error: {“error”: “invalid_request”, “error_description”: “unknown field "access_token"”}
