< Back to all integrations

Dropbox

Data & Infrastructure

Connect AI agents and workflows to Dropbox: upload, download, move and share files, restore revisions, collect files with file requests, and act on new files.

Book a demo
[ Dropbox + engini ]

Dropbox for AI agents and workflows.

engini lets your AI agents and workflows work in Dropbox: upload, download, copy, move, rename and delete files and folders, restore earlier revisions, create and manage share links, and collect files from people outside the company with file requests, with a trigger on new files. Connect from Claude, ChatGPT or Cursor over MCP, from your code, or build in Workflow Studio.

MCPPython and TypeScript SDKCLIREST APIWorkflow Studio
Read the Dropbox guide →
Sign-inOAuth 2, through engini or your own Dropbox app
ReachFiles, folders, revisions, share links and file requests
TriggerNew files, on a schedule
[ 01 / What agents can do ]

What your agent can do in Dropbox. Every tool is one you allow or leave out.

The Dropbox tools in engini, grouped by what they change. Read tools are safe to hand out widely. Write and delete tools go only to the agents that need them.

Read

Get Files and Folders, Get Folder Contents, Get File, Download File

Find and read files.

Read
Get File Revisions

Read a file's history.

Read
Get File Requests, Get File Request

Read file requests.

Read

Write

Upload File, Create or Update Text File

Write files.

Write
Copy File Or Folder, Move Folder Or File, Rename File or Folder, Create Folder

Organize.

Write
Restore File

Bring back an earlier revision.

Write
Create Share Link, Update Share Link

Share.

Write
Create File Request, Update File Request

Ask someone outside for files.

Write

Delete

Delete File Or Folder, Delete Share Link, Delete Closed File Requests

Remove files, links and old requests.

Delete

Any endpoint

Send API Request

Call any Dropbox API endpoint, with the sign-in added for you.

Any call

Triggers

Check for New Files

New files in the folder you choose.

Scheduled

A trigger starts a workflow, and a workflow can include an AI agent step. In Code, a trigger delivers the event to your own endpoint.

[ 02 / Connect your agent ]

Connect your AI agent to Dropbox. Four ways in, one set of permissions.

MCP

Claude, ChatGPT, Cursor

Create an MCP server in engini with your Dropbox connection and only the tools you choose. Add its address to your client and sign in through engini. There is no key to copy.

MCP client setup →
SDK

Python and TypeScript

Hand your agent a toolset of Dropbox tools. The SDK gives OpenAI and Anthropic models the tools in the format they expect and runs the ones they pick.

SDK guide →
CLI

For coding agents

The engini CLI connects Dropbox and runs its tools from a terminal, with machine-readable output, so an AI coding agent can drive it without getting stuck.

CLI guide →
REST API

Any language

Every Dropbox tool is an endpoint. Call it with exact inputs from a scheduled job or a sync, with no model in the loop.

API reference →
MCP in four steps
In engini, connect Dropbox and create an MCP server with that connection and the tools this agent may use.
Claude: Settings, Connectors, Add custom connector, then paste the server address.
Cursor: add the address to .cursor/mcp.json. Claude Code: claude mcp add.
Sign in through engini when the client asks. The agent sees only the tools you chose.
Cursor, connected to Dropbox through engini
// .cursor/mcp.json: Cursor, connected to Dropbox through engini
{
"mcpServers": {
"engini-dropbox": {
"url": "<your engini MCP server address>"
}
}
}

Create the MCP server in engini with your Dropbox connection and the tools this agent may use, then paste its address. The client signs in through engini on first use. Claude, VS Code and other clients take the same address: see the MCP client setup guide.

Try asking your agent
“Ask Acme for their W-9 with a file request.”
“Which files arrived in the vendor folder today?”
“Share the signed contract with the customer.”
“Restore yesterday's version of the price list.”
“Move processed invoices to the archive folder.”
“Find the onboarding packet for Globex.”

Each request runs through the Dropbox tools in the agent's toolset or MCP server. If a tool is not allowed, the agent cannot call it.

[ 03 / What teams build ]

What teams build on Dropbox. Agents and workflows, across systems.

Accounts payable

Vendor documents, collected

A file request collects W-9s and invoices from vendors, and new files are entered in the ERP.

DropboxNetSuite
Sales

Contracts shared on close

When a deal closes, share the signed contract with the customer and attach the link to the account.

SalesforceDropbox
Operations

New files that start work

A new file in a folder starts a workflow that reads it and files it.

DropboxSAP S/4HANA
Knowledge

Find the right file

An agent in Claude searches folders and answers from the files. Its toolset holds read tools only.

DropboxClaude

Every integration runs both ways, so any of these flows can also run in reverse. These are examples, not the limit: any flow between Dropbox and another system engini connects is available.

[ 04 / Agent Policy ]

You decide what each agent may do in Dropbox. engini enforces it on every call.

Toolsets

Only the tools you allow

A toolset lists the Dropbox tools an agent may call and the connection each one uses. Give one agent read tools only and another the write it needs. engini refuses any call outside the toolset.

MCP servers

Scoped when you set them up

An MCP server exposes only the connections and tools chosen when it is created, and engini shows who uses each server.

Identity

Whose permissions apply

Connect a person's own Dropbox account and engini acts as that person, with their Dropbox permissions. Use a shared integration account and it acts as that account. Every run is recorded under the user who started it.

Credentials

Kept out of prompts

Your agent never needs your credentials: engini stores them and adds them when it runs each call, so keys stay out of prompts and tool inputs.

Audit

Every call on record

Every call lands in History and the audit log, which you can export or stream to your SIEM.

Environments

Test before production

Workspaces keep teams apart, and development, staging and production environments keep a test agent away from live data.

SOC 2 Type IIISO 27001GDPRSecurity at engini →
[ 05 / Set up ]

Connect Dropbox in three steps. Then decide what each agent may do.

Step 01

Sign in to Dropbox

Add a Dropbox connection and sign in through engini, or use your own Dropbox app.

Step 02

Choose the tools

Add the connection to an MCP server or a toolset with only the tools each agent needs.

Step 03

Build or ask

Use the connection as a step in a workflow, or ask your agent to work in Dropbox from Claude, ChatGPT, Cursor or your own code.

Full Dropbox setup guide →
[ 06 / Questions ]

Dropbox and engini. Straight answers.

Can an AI agent write to Dropbox, or only read?

Both. engini has tools to upload, copy, move, rename, restore and delete files and folders, share them and manage file requests. Whether a given agent may use them is up to you: give it a toolset or an MCP server with read tools only, and it cannot call the rest.

Does the agent act as me in Dropbox?

It acts as the Dropbox account behind the connection, with that account's access. Every run is recorded under the person who started it.

Can a change in Dropbox start work?

Yes. A scheduled trigger checks for new files in the folder you choose. The workflow can include an AI agent step.

What if the tool I need is not listed?

Use Send API Request to call any Dropbox API endpoint through the same connection, and give it only to the agents that need it.