Dropbox

List, search and inspect Dropbox files and folders, create folders, move or rename items, and manage file requests and shared-link listings.

Organise client and project folders automatically and collect documents with file requests.

Build a flow with Dropbox Provider API documentation

Source actions

Destination actions

Data types

Validation status

Implemented · fixture tested.

Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.

What you can map

account

Get account
Source
The authorised Dropbox account.

file requests

Create file request
Destination
Not retried automatically
Creates a file request that lets others upload into a folder.
List file requests
Source
File requests owned by the user.
Update file request
Destination
Duplicate protected
Changes a file request's title, destination, description or open state.

file revisions

List file revisions
Source
Previous revisions of a file.

files

Get metadata
Source
Metadata for a file or folder.
Search files
Source
Files and folders matching a query by name and, on supported plans, content.
Move or rename
Destination
Duplicate protected
Moves or renames a file or folder.

folder entries

List folder
Source
Files and folders in a folder, optionally recursive.

folders

Create folder
Destination
Duplicate protected
Creates a folder at a path. Fails if something already exists there.

shared links

List shared links
Source
Shared links the user created, optionally for one path.

Authentication

Dropbox app key, app secret and refresh token

Plans and access

All Dropbox plans; team-space access needs the Dropbox-API-Path-Root header (not used here). Requires a Dropbox app with the files.metadata, files.content and sharing scopes chosen.

Test environment

Use a development-status app with a test Dropbox account.

Rate limits

Per-user and per-app limits that Dropbox does not publish; HTTP 429 with Retry-After.

Provider events

Dropbox webhooks notify of changed accounts; changes are read with list_folder cursors. Nexra event triggers are not yet available; flows run on demand or on a schedule.

Before you build a flow

File contents are not uploaded or downloaded; content endpoints use the separate content.dropboxapi.com host and are not implemented.
Deletes, shared-link creation and sharing changes are not implemented; shared links are read-only.
Paths resolve in the user's home namespace; Dropbox team spaces need a Dropbox-API-Path-Root header that this recipe does not send.
File request creation has no idempotency key; uncertain creates are not repeated automatically.