🇬🇧 EN

📥 Dropbox Watch

Polls a Dropbox folder for new files and fires a workflow run whenever one appears. Requires Dropbox OAuth credentials configured in Settings → Integrations.

Category: Triggers · Type identifier: dropbox_watch

Overview

The Dropbox Watch trigger works by periodically checking a specified Dropbox folder for files that have appeared since the last check. When a new file is found, Flusso starts a workflow run and passes the file's details — name, path, size, and modification timestamp — as output variables available to all downstream nodes.

This trigger is particularly useful for teams that use Dropbox as a shared inbox: partners upload export files, clients submit forms as attachments, or internal tools drop generated reports into a folder. Instead of someone manually checking the folder and kicking off processing, the Dropbox Watch trigger handles the monitoring automatically.

To use this trigger, your Dropbox account must be connected in Flusso. Navigate to Settings → Integrations and connect your Dropbox account before configuring this trigger. Once connected, credentials are reused by all Dropbox nodes across your workflows.

Configuration

Field	Status	Description
Credential	Required	Dropbox account credential from Settings → Integrations.
Folder Path	Required	The Dropbox folder path to monitor, e.g. `/uploads/invoices`. Use `/` for the root folder.
Poll Interval	Optional	Check frequency in minutes. Default: 5.
File Extension Filter	Optional	Comma-separated extensions, e.g. `.pdf,.docx`. Leave blank for all files.

Output Data

Each workflow run triggered by this node receives the following fields describing the newly detected file.

Field	Type	Description
`file.path`	string	Full path to the file in Dropbox
`file.name`	string	Filename with extension
`file.size`	number	File size in bytes
`file.modified_at`	string	ISO 8601 last-modified timestamp
`file.id`	string	Dropbox unique file ID

{{ trigger.output.file.path }} {{ trigger.output.file.name }} {{ trigger.output.file.size }} {{ trigger.output.file.modified_at }} {{ trigger.output.file.id }}

Example Usage

Watch a Dropbox folder for new CSV exports, then import them into a database.

Add a Dropbox Watch trigger. Set the Folder Path to /exports/weekly, set Poll Interval to 10, and set File Extension Filter to .csv.
Add a Dropbox read node. Pass {{ trigger.output.file.path }} as the path to download the file's contents.
Add a Transform node to parse and reshape the CSV data into the structure your downstream steps expect.
Add an HTTP Request node to POST each row to your database API endpoint.

Tips & Notes

Subfolders are not monitored. Flusso only detects files added directly inside the configured folder path. Files added to subfolders are ignored. Create separate workflows for each subfolder if needed.
One run per file. If multiple files are added between two polls, a separate workflow run is started for each new file.
Files are tracked by name and ID. Flusso compares the current folder contents to the previous poll. Use unique, timestamped file names to avoid ambiguity when files are replaced.
Reconnect if your Dropbox token expires. If the trigger stops working, go to Settings → Integrations and reconnect your Dropbox account.

Related Nodes

Google Drive Watch — the equivalent trigger for Google Drive folders.
Local File Watch — watch a directory on the server filesystem.
HTTP Request — call external APIs after processing a file.