Automate Dropbox File Operations

A tool-usage skill for automating Dropbox through Composio's Rube MCP server rather than calling the Dropbox API directly. Covers five core workflows with their exact tool call sequences: searching files and folders (DROPBOX_SEARCH_FILE_OR_FOLDER with query, path scope, file_categories and file_extensions filters, paginated via DROPBOX_SEARCH_CONTINUE up to a 10,000-match cap); uploading and downloading (DROPBOX_UPLOAD_FILE with add or overwrite mode and autorename, DROPBOX_READ_FILE, DROPBOX_DOWNLOAD_ZIP for a whole folder under 20GB with no file over 4GB and under 10,000 entries, DROPBOX_SAVE_URL for saving a public URL directly, which is asynchronous and can take up to 15 minutes, and DROPBOX_EXPORT_FILE for non-downloadable Paper docs to markdown, HTML, or plain text); sharing (DROPBOX_CREATE_SHARED_LINK with audience, access, expires, and password settings, checking DROPBOX_LIST_SHARED_LINKS first since creating a duplicate link returns a 409 Conflict); folder management (DROPBOX_CREATE_FOLDER, DROPBOX_MOVE_FILE_OR_FOLDER, DROPBOX_DELETE_FILE_OR_FOLDER, and their _BATCH variants, polled via DROPBOX_CHECK_MOVE_BATCH or DROPBOX_CHECK_FOLDER_BATCH, noting the all-or-nothing v1 DROPBOX_FILES_MOVE_BATCH versus the preferred v2 DROPBOX_MOVE_BATCH); and listing folder contents (DROPBOX_LIST_FILES_IN_FOLDER with recursive, limit, and include_deleted options, using an empty string rather than a slash for root). It documents cross-cutting patterns: path-based versus id:-prefixed resolution, always reusing the canonical path_display or path_lower from DROPBOX_GET_METADATA rather than user-typed paths since casing can differ, cursor-based pagination across search, listing, and shared-link endpoints, and which operations return an async job ID to poll.

Use when an agent needs to search, upload, download, share, move, copy, delete, or list Dropbox content through Rube MCP - the skill assumes RUBE_SEARCH_TOOLS is available and an ACTIVE Dropbox connection exists via RUBE_MANAGE_CONNECTIONS before any workflow runs. Not applicable without Rube MCP connected, and not the right reference for calling the raw Dropbox API directly - the tool names and parameters here are Composio's Dropbox toolkit wrapper, not the underlying Dropbox SDK.

Inputs are Dropbox paths (must start with a slash, case-sensitive, must not end with a slash or trailing whitespace; use an empty string only for root on supported endpoints) or file content payloads for upload. Outputs are file or folder metadata, search results with cursor-based pagination, shared link URLs and their settings, or async job IDs for batch move, delete, or folder-create operations that must be polled to completion.

Runs entirely through Composio's Rube MCP server (https://rube.app/mcp, no API keys required) and its Dropbox toolkit, authenticated via Dropbox OAuth through RUBE_MANAGE_CONNECTIONS.

Agent builders wiring up Dropbox file operations through Rube MCP who need the exact tool names, required parameters, and documented pitfalls - pagination caps, async timeouts, case-sensitivity, duplicate-link conflicts - rather than trial-and-error against the toolkit.