Skip to main content
This document covers export_to_dropbox (display name Dropbox Export), which downloads a platform or HTTP file URL and uploads its bytes to the connected Dropbox account. Dropbox is a native REST integration, not an MCP or Composio tool.

​
Authentication and enablement

The tool uses the Dropbox OAuth connector. The access token is injected through x-variable-service: "dropbox" and is not shown as a per-run input. Dropbox API and content calls use the audited HTTP transport. Off by default. Enable the tool explicitly for each agent that needs Dropbox export. Dropbox Business accounts resolve root_namespace_id and send Dropbox-API-Path-Root, preserving legacy uploads into the team space.

​
Inputs

Required:
  • file_url: source file URL, such as a platform storage URL or output from another file-producing tool.
  • destination_path: complete absolute Dropbox path including the file name, such as /Reports/report.csv.
Optional:
  • conflict_mode:
    • autorename (default): preserve the legacy behavior, keeping both files and letting Dropbox choose a unique name.
    • add: fail when the destination already exists.
    • overwrite: replace the existing file.
  • mime_type: output MIME type; inferred from the uploaded name when omitted.
Destination paths reject empty, ., and .. components.

​
Upload behavior

  • Exports are limited to 250 MB.
  • Empty source files are rejected explicitly.
  • Files up to 8 MB use Dropbox’s simple upload endpoint.
  • Larger files use an upload session with 8 MB chunks.
  • Read requests may be retried; upload and session mutations are not blindly replayed after an ambiguous response.
  • Missing destination parent folders are created component by component, matching the legacy Dropbox export folder picker.

​
Output

The structured result contains dropbox_id, file_name, destination_path, revision, content_hash, mime_type, file_size, conflict_mode, and completed_at.

​
Errors

  • Missing source URL, malformed destination path, or unknown conflict mode fails validation before upload.
  • Source download, size, Dropbox conflict, and upload-session failures return a structured tool error.
  • Tokens, paths, response bodies, and file content are never written to logs. Errors carry the HTTP status plus, when Dropbox reports one, the union tag or the name of a scope the app has not been granted. A missing write scope fails as a 400; grant it in the Dropbox App Console and reconnect the integration.