Dropbox Folder Provisioning for New Clients

Overview

This flow standardizes Dropbox client-workspace setup. When a new client row is created in Dataverse, it provisions a consistent Dropbox folder structure from a template, writes the resulting path and a navigation link back onto the client record, and notifies the operations team in Microsoft Teams.

Why it matters: manual folder setup is inconsistent and slow. Templated provisioning gives every client a uniform, predictably-named Dropbox workspace the moment the record is created - no human steps.

Connector scope note: the standard Dropbox connector exposes only file/folder CRUD (no create-shared-link, add-member, or file-request operations), so this build provisions folders with real CreateFolder calls and provides a derived navigation deep-link instead of an API-created share link. See the customization guide to add true sharing via HTTP + the Dropbox API.

Ships Off (demo).

Use Case

A services/operations team wants every new client to get the same Dropbox structure automatically: a top-level folder named Client Name - CODE plus a standard set of subfolders (contracts, deliverables, invoices, uploads, correspondence). The folder path and an open-in-Dropbox link are stored on the client record so anyone can jump straight to the workspace.

Flow Architecture

Environment Variables

Connectors & Connections

Note — All connections are referenced as solution connection references; the flow is portable between environments as long as a connection is mapped at import time.

Customization Guide

Almost every realistic variant of this flow can be implemented by changing environment variable values. A few cases require small edits inside the flow definition — those are called out explicitly below.

Folder structure

Edit flowlibs_FolderTemplate (JSON array) to change the standard subfolders; edit flowlibs_DropboxClientRootPath to relocate the client root. No flow edits needed.

Naming convention

Adjust Compose Client Folder Name to change how the top-level folder name is built (e.g. include region or onboarding date).

Real sharing / file requests

The Dropbox connector cannot create shared links, add members, or open file requests. Append an HTTP action calling the Dropbox API (/2/sharing/create_shared_link_with_settings, /2/sharing/add_folder_member, /2/file_requests/create) with an OAuth token stored in a Key Vault-backed env var, then write the returned link to a new column.

Offboarding

Add a sibling flow on client-close to archive or rename the folder.

Key Expressions

The flow is intentionally light on Power Fx / WDL gymnastics — the heaviest expressions are the branch-name concatenation and the approval outcome check. They are listed below in the order they appear in the flow.

concat(variables('varClientName'),' - ',variables('varClientCode'))

concat(variables('varClientRootPath'),'/',outputs('Compose_Client_Folder_Name'))

json(variables('varFolderTemplate'))

concat(variables('varDropboxWebBase'),replace(outputs('Compose_Client_Folder_Path'),' ','%20'))

triggerOutputs()?['body/flowlibs_clientonboardingid']