OneDrive for Business connector

When to use this connector

Use this connector to create flows that work with files in Microsoft OneDrive for Business.

Creating a connection

Step 1. In the Connections window click the + button, type in ondedrive.

Step 2. Select OneDrive for Business.

Step 3. Enter connection parameters.

Connection Parameters

• Organization Domain - your Office 365 domain, for example etlworks.

The actual OneDrive endpoint is https://domain-my.sharepoint.com/personal/username, for example https://etlworks-my.sharepoint.com/personal/user_etlworks_com but we do all the trickery internally so all you really need is your organization Office 365 domain name and a user name.

• Directory - the actual directory with files. This parameter is optional.
• Files - the actual file name or a wildcard file name, for example, *.csv.
• User - username.
• Password - password.
• Add Suffix When Creating Files in Transformation - you can select one of the predefined suffixes for the files created using this connection. For example, if you select uuid as a suffix and the original file name is dest.csv, Integrator will create files with the name dest_uuid.csv, where uuid is a globally unique identifier such as 21EC2020-3AEA-4069-A2DD-08002B30309D.

This parameter works only when the file is created using source-to-destination-transformation. Read how to add a suffix to the files created when copying, moving, renaming, and ziping files.

• Enable Wildcard File Name - if there are multiple source files in a folder, you can specify an algorithm which will be used to select the next source file to process. For example, if Files is set to *.csv and oldest is selected, Integrator will always select the oldest file in the folder which matches the wildcard *.csv.
• Override Wildcard File Name set for Connection - if Wildcard File Names are allowed, Override Wildcard File Name set for Connection is enabled, and the file name entered in the FROM field of the transformation is a wildcard file name, the system will override the file name entered at the connection level. Otherwise, the default behavior is to use the wildcard file name entered when the connection was configured.