DropBox Connector for SSIS

In this article you will learn how to quickly and efficiently integrate DropBox data in SSIS without coding. We will use high-performance DropBox Connector to easily connect to DropBox and then access the data inside SSIS.

Read / write DropBox data inside your app; perform many DropBox operations without coding, just use easy to use high performance API Connector for DropBox

Let's follow the steps below to see how we can accomplish that!

Download Documentation

DropBox Connector for SSIS is based on ZappySys API Connector Framework which is a part of SSIS PowerPack. It is a collection of high-performance SSIS connectors that enable you to integrate data with virtually any data provider supported by SSIS, including SQL Server. SSIS PowerPack supports various file formats, sources and destinations, including REST/SOAP API, SFTP/FTP, storage services, and plain files, to mention a few (if you are new to SSIS and SSIS PowerPack, find out more on how to use them).

Connect to DropBox in other apps

Connect to DropBox in SQL Server

Connect to DropBox in Power BI

Connect to DropBox in SSRS

Connect to DropBox in Informatica

Connect to DropBox in MS Access

Connect to DropBox in MS Excel

Connect to DropBox in SSAS

Connect to DropBox in C#

Connect to DropBox in Python

Connect to DropBox in JAVA

Connect to DropBox in Tableau

Connect to DropBox in SAP Crystal Reports

Connect to DropBox in Azure Data Factory (Pipeline)

Connect to DropBox in Azure Data Factory (SSIS)

Connect to DropBox in Talend Studio

Connect to DropBox in UiPath

Connect to DropBox in PowerShell

Connect to DropBox in ODBC

Video Tutorial - Integrate DropBox data in SSIS

This video covers following and more so watch carefully. After watching this video follow the steps described in this article.

How to download / install required driver for DropBox integration in SSIS
How to configure connection for DropBox
Features about API Source (Authentication / Query Language / Examples / Driver UI)
Using DropBox Connection in SSIS

Watch this video on YouTube

Prerequisites

Before we begin, make sure the following prerequisites are met:

SSIS designer installed. Sometimes it is referred as BIDS or SSDT (download it from Microsoft).
Basic knowledge of SSIS package development using Microsoft SQL Server Integration Services.
SSIS PowerPack is installed (if you are new to SSIS PowerPack, then get started!).

Read data from DropBox in SSIS (Export data)

In this section we will learn how to configure and use DropBox Connector in API Source to extract data from DropBox.

Begin with opening Visual Studio and Create a New Project.
Select Integration Service Project and in new project window set the appropriate name and location for project. And click OK.
In the new SSIS project screen you will find the following:
1. SSIS ToolBox on left side bar
2. Solution Explorer and Property Window on right bar
3. Control flow, data flow, event Handlers, Package Explorer in tab windows
4. Connection Manager Window in the bottom
Note: If you don't see ZappySys SSIS PowerPack Task or Components in SSIS Toolbox, please refer to this help link.
Now, Drag and Drop SSIS Data Flow Task from SSIS Toolbox. Double click on the Data Flow Task to see Data Flow designer.
From the SSIS toolbox drag and API Source (Predefined Templates) on the data flow designer surface, and double click on it to edit it:
Select New Connection to create a new connection:
Use a preinstalled DropBox Connector from Popular Connector List or press Search Online radio button to download DropBox Connector. Once downloaded simply use it in the configuration:

DropBox
Proceed with selecting the desired Authentication Type. Then select API Base URL (in most cases default one is the right one). Finally, fill in all the required parameters and set optional parameters if needed. You may press a link Steps to Configure which will help set certain parameters. More info is available in Authentication section.
User Account [OAuth]
Steps how to get and use DropBox credentials : User Account [OAuth]

To use OAuth authentication, firstly, you need to create OAuth application:

Log into your DropBox account.

Go to DropBox My Apps.

Then press Create app button to create a new app:

Once a new page opens, select Scoped access option:

Next, select Full Dropbox to access all files and folders or App folder to access specific folder's files and folders option.

Continue by giving your app a name.

Then check I agree to Dropbox API Terms and Conditions checkbox.

Click Create app button.

Once a new page opens, click Enable additional teams and Enable additional users buttons:

Then copy App key and App secret and copy paste them into your favorite text editor (you will need them later).

Proceed by setting a Redirect URI and clicking Add button.
NOTE: If you don't have a working Redirect URI, you can use https://zappysys.com/oauth (it's safe).

Then click on Permissions tab and select application scopes:

Select all Individual Scopes and Team Scopes if you want to manage team data.

Click Submit button.

Now go to SSIS package or ODBC data source and in User Account authentication set these parameters:

For ClientId field use App key value.

For ClientSecret field use App secret value.

For ReturnUrl field use Redirect URI value.
Done! Now you are ready to use Dropbox Connector!

NOTE: If you are planning to use your current data connection/token for automated processes, we recommend that you use a generic account for token generation when the login box appears (e.g. sales_automation@mycompany.com instead of bob_smith@mycompany.com). When you use a personal account which is tied to a specific employee profile and that employee leaves the company, the token may become invalid and any automated processes using that token will fail. Another potentially unwanted effect of using a personal token is incorrect logging; the API calls (e.g. Read, Edit, Delete, Upload) made with that token will record the specific user as performing the calls instead of an automated process.

Configuring authentication parameters

DropBox

User Account [OAuth]

https://api.dropboxapi.com/2/

Required Parameters
UseCustomApp	Fill-in the parameter...
ReturnUrl	Fill-in the parameter...
Optional Parameters
ClientId
ClientSecret
Scope
RetryMode	RetryWhenStatusCodeMatch
RetryStatusCodeList	429
RetryCountMax	5
RetryMultiplyWaitTime	True

Parameter	Description
TargetFilePath	Specify a file path in DropBox to save file to
SourceFilePath	Specify a disk file path to upload

Parameter	Description
Url	API URL goes here. You can enter full URL or Partial URL relative to Base URL. If it is full URL then domain name must be part of ServiceURL or part of TrustedDomains
IsMultiPart	Set this option if you want to upload file(s) (i.e. POST RAW file data) or send data using Multi-Part encoding method (i.e. Content-Type: multipart/form-data). Multi-Part request allows you to mix key/value and upload files in same request. On the other hand raw upload allows only single file upload (without any key/value) ==== Raw Upload (Content-Type: application/octet-stream) ===== To upload single file in raw mode check this option and specify full file path starting with @ sign in the Body (e.g. @c:\data\myfile.zip ) ==== Form-Data / Multipart Upload (Content-Type: multipart/form-data) ===== To treat your Request data as multi part fields you must specify key/value pairs separated by new lines into RequestData field (i.e. Body). Each key value pair is entered on new-line and key/value are separated using equal sign (=). Preceding and trailing spaces are ignored also blank lines are ignored. If field value has some any special character(s) then use escape sequence (e.g. For NewLine: \r\n, For Tab: \t, For at (@): \@). When value of any field starts with at sign (@) its automatically treated as File you want to upload. By default file content type is determined based on extension however you can supply content type manually for any field using this way [ YourFileFieldName.Content-Type=some-content-type ]. By default File Upload Field always includes Content-Type in the request (non file fields do not have content-type by default unless you supply manually). For some reason if you dont want to use Content-Type header in your request then supply blank Content-Type to exclude this header altogather [e.g. SomeFieldName.Content-Type= ]. In below example we have supplied Content-Type for file2 and SomeField1, all other fields are using default content-type. See below Example of uploading multiple files along with additional fields. If some API requires you to pass Content-Type: multipart/form-data rather than multipart/form-data then manually set Request Header => Content-Type: multipart/mixed (it must starts with multipart/ else will be ignored). file1=@c:\data\Myfile1.txt file2=@c:\data\Myfile2.json file2.Content-Type=application/json SomeField1=aaaaaaa SomeField1.Content-Type=text/plain SomeField2=12345 SomeFieldWithNewLineAndTab=This is line1\r\nThis is line2\r\nThis is \ttab \ttab \ttab SomeFieldStartingWithAtSign=\@MyTwitterHandle
Filter	Enter filter to extract array from response. Example: $.rows[] --OR-- $.customers[].orders[*]. Check your response document and find out hierarchy you like to extract
Headers	Headers for Request. To enter multiple headers use double pipe (\|\|) or new line after each {header-name}:{value} pair