Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Dropbox

Automate file and folder workflows across Dropbox and connected systems.

CategoryProductivity
AuthenticationOAuth 2.0
Version0.8.0
Published scopes4 published scopes
Last updatedSeptember 19, 2026

Overview

Connect Dropbox with Flows360

Automate file and folder workflows across Dropbox and connected systems.

Use the Dropbox connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 14 actions and 1 trigger.

Available actions

  • Search
  • Create New Text File
  • Upload file
  • Download File
  • Get temporary file link
  • Delete file
  • Move file
  • Copy file
  • Plus 6 additional declared actions.

Available triggers

  • New Folder

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Dropbox
  • Package: @activepieces/piece-dropbox@0.8.0
  • Exact artifact digest: sha256:63a1875cb9dd7365e4bd34e2a7ab0d8a34fb6e150f26b1a4fb27e0500a709435
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

OAUTH2. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Search (search_dropbox), Search for files and folders Classification: read.
  • Create New Text File (create_new_dropbox_text_file), Create a new text file from text input Classification: read.
  • Upload file (upload_dropbox_file), Upload a file Classification: read.
  • Download File (downloadFile), Download a File from Dropbox Classification: read.
  • Get temporary file link (get_dropbox_file_link), Get a temporary file link Classification: read.
  • Delete file (delete_dropbox_file), Delete a file Classification: read.
  • Move file (move_dropbox_file), Move a file Classification: read.
  • Copy file (copy_dropbox_file), Copy a file Classification: read.
  • Create New Folder (create_new_dropbox_folder), Create a new empty folder Classification: read.
  • Delete folder (delete_dropbox_folder), Delete a folder Classification: read.
  • Move folder (move_dropbox_folder), Move a folder Classification: read.
  • Copy folder (copy_dropbox_folder), Copy a folder Classification: read.
  • List a folder (list_dropbox_folder), List the contents of a folder Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Folder, polling.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

AuthenticationOAuth 2.0
Supported objects15
Supported actionsNot published
TriggersNone published

Authentication

Authentication method: OAuth 2.0

Required scopes

files.metadata.writefiles.metadata.readfiles.content.writefiles.content.read

Authentication profiles

connection · oauth2

OAuth scopes: files.metadata.write, files.metadata.read, files.content.write, files.content.read

Supported objects

ObjectReadWriteNotes
Search Yes No Search for files and folders
Create New Text File Yes No Create a new text file from text input
Upload file Yes No Upload a file
Download File Yes No Download a File from Dropbox
Get temporary file link Yes No Get a temporary file link
Delete file Yes No Delete a file
Move file Yes No Move a file
Copy file Yes No Copy a file
Create New Folder Yes No Create a new empty folder
Delete folder Yes No Delete a folder
Move folder Yes No Move a folder
Copy folder Yes No Copy a folder
List a folder Yes No List the contents of a folder
Custom API Call Yes No Make a custom API call to a specific endpoint
New Folder Yes No polling trigger declared by the pinned package.

Setup

Setup

  1. Add the Dropbox connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.

OAuth scopes

  • files.metadata.write
  • files.metadata.read
  • files.content.write
  • files.content.read
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-dropbox@0.8.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 14 actions and 1 trigger declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Dropbox connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-dropbox@0.8.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com