Forum Discussion

BradLemke's avatar
BradLemke
Qrew Assistant Captain
6 years ago

Pipelines | Dropbox & Webhooks assist.

Goal:  Utilize a third-party file storage service due to the economics of storing photos on Quickbase, but still maintain the ability to display the photos in a notification email. Method: Using pi...
Pipelines
BradLemke's avatar
BradLemke
Qrew Assistant Captain
6 years ago
That was my train of thought, to rule out as much as we can from Quickbase before moving to Dropbox.

When you log into your Dropbox account @ https://www.dropbox.com/developers/apps/, did you create an app that has 'Full Account Access?' 

I created my app before they did their latest API update, so setting up an identical app to what works for mine would use their legacy (supposedly not recommended) API.
​
Let me know if this helps at all.

------------------------------
Brad Lemke
------------------------------
QuickBaseJunkie's avatar
QuickBaseJunkie
Icon for Qrew Legend rankQrew Legend
6 years ago
Very interesting @Brad Lemke, I hadn't set up a developer app in Dropbox as I don't need a share link.

For the initial upload did you authenticate to Dropbox with your developer app? Or a user account? When I authenticated it pulled my credentials from my browser as I was already logged into Dropbox.​

------------------------------
Sharon Faust (QuickBaseJunkie.com)
Founder, Quick Base Junkie
https://quickbasejunkie.com
------------------------------
  • BradLemke's avatar
    BradLemke
    Qrew Assistant Captain
    6 years ago
    Apologies for the confusion, the Dropbox App is for the custom Pipelines Webhook/JSON Handler API commands to Dropbox later in my particular use-case.  The App is not necessary at all for simply uploading to Dropbox.  I confirmed this by creating a fresh Dropbox Personal User Account, free version, and no Dropbox settings adjusted before pointing my Pipeline at it - meaning it's likely safe to assume now that it is one obscure little thing in Quickbase that I've been forgetting about.

    That one obscure little thing might be in the URL Formula itself: Try hardwriting out the first half of the URL:
    • "https://realm.quickbase.com/up/tableid/a/r" & [Record ID#] & "e9/v0"
      • Adjust the bolded portion as needed.


    ------------------------------
    Brad Lemke
    ------------------------------
  • QuickBaseJunkie's avatar
    QuickBaseJunkie
    Icon for Qrew Legend rankQrew Legend
    6 years ago
    @Brad Lemke that was it! I recall having to do this when inserting a link into a notification with HTML... tricky-tricky!

    I also noticed that I need to name the file through the pipeline with the file extension or it won't recognize the file type in Dropbox.

    Cheers! I owe you a coffee or beer! Thank you so much!

    -Sharon
    ​

    ------------------------------
    Sharon Faust (QuickBaseJunkie.com)
    Founder, Quick Base Junkie
    https://quickbasejunkie.com
    ------------------------------
  • ZintJoseph's avatar
    ZintJoseph
    Qrew Captain
    5 years ago
    I know this is an old post but hoping for one additional item out of this. I was able to take this and get my file uploaded to DB. The reason I need this function is to be able to send a file larger than one that can be emailed. I know want to create the share link from the file in DP, bring that link back into QB, and send that link in a notification. Pipelines does not have a Get File Link option so thinking this is going to have to be done with some API code on the DB side to get the link.

    ------------------------------
    Joey Zint
    ------------------------------
  • QuickBaseJunkie's avatar
    QuickBaseJunkie
    Icon for Qrew Legend rankQrew Legend
    5 years ago
    @Joey Zint I believe your answer is already in this thread (reply 7) when used in combination with the Dropbox API Documentation.

    But let me expand.

    You'll need 2 steps to access the sharable link.

    1) Fetch JSON
    Type: POST

    Headers:
    Authorization: Bearer XXXXXXXXXX <-- Replace with your Dropbox authorization
    Content-Type: application/json​​

    Body:
    {
    "path": "{{b.path}}", <-- where b.path is the path from a prior Dropbox Upload File step
    "settings": {
    }
    }

    JSON URL: https://api.dropboxapi.com/2/sharing/create_shared_link_with_settings

    2) Iterate over JSON records
    JSON Sample Schema:
    Copied "Return" sample from this Dropbox API Documentation:
    From the iterate JSON step, you can then access the URL to populate in your Quickbase/email.

    Please note I'm not currently using this Pipeline but set it up for testing purposes. At which time it was functioning as expected.

    Let me know if this helps 👍
    -Sharon

    ------------------------------
    Sharon Faust (QuickBaseJunkie.com)
    Founder, Quick Base Junkie
    https://quickbasejunkie.com
    ------------------------------
  • ZintJoseph's avatar
    ZintJoseph
    Qrew Captain
    5 years ago
    Thank you so much....that was what I needed. Everything is working. I just need to refine the process to create a folder, place the file there, and update the existing file if there are changes in QB. This is not a process that is going to run very much. I just need an option to place large files that cannot be emailed into DropBox and send a link in a notification for them to download.

    This is my first pipeline, so pretty stoked that it works. I have done some Microsoft Flows with QuickBase and this is very similar.

    ------------------------------
    Joey Zint
    ------------------------------