File Added or Updated
Receive eligible new or updated file changes after connection, optionally filtered by folder prefixes and extensions. Folder prefixes include nested folders; folder and deletion events do not send mail.
Workflow template
Email a fixed recipient when a Dropbox file is added or updated. Each plain-text Gmail notice includes name, path, size, server modification time and file ID, while file contents and attachments stay in Dropbox.
How it works
Receive eligible new or updated file changes after connection, optionally filtered by folder prefixes and extensions. Folder prefixes include nested folders; folder and deletion events do not send mail.
Send a fixed subject and plain-text metadata to the configured recipient through Gmail. The message uses server_modified, includes no attachment or public sharing link and leaves a copy in Sent.
The result
Dropbox file added or updated
A Dropbox file was added or updated. Name: Grüße aus München.txt Path: /Example Documents/Grüße aus München.txt Size (bytes): 42 Server modified (UTC): 2026-09-19T09:00:00Z File ID: id:fictional-dropbox-file-42 File contents stay in Dropbox. No attachment or public sharing link is included.
Fictional file sample. The fixed recipient starts blank and must be configured; this example sends no email or file.
Before activation
Connect Dropbox and review optional folder-prefix and file-extension filters. An empty folder filter covers eligible changes across the connected account; start with an isolated test folder.
Connect Gmail with send permission and enter the destination address in the action. Start with your own address and review whether file names and paths are suitable for that recipient.
Activate and wait for Connected. Upload a controlled file, then verify its name, path, byte size, server modification timestamp and file ID in the email and Gmail Sent.
Adds and updates share the same notice. The trigger does not distinguish between them in the prepared email. Existing files are not imported; folder and deletion events are excluded.
This is a notification rather than a file copy. File contents, attachments and public sharing links are not included. Names and paths are still visible to the recipient, and the timestamp is Dropbox server_modified rather than send time.
Sending limits and duplicates apply. Gmail stores a Sent copy and requires send permission. Manual reruns or ambiguous provider failures may send another email; this is not bulk outreach or bidirectional file synchronization.
No. It includes name, path, byte size, server modification time and file ID. The file stays in Dropbox, no attachment is sent and no public sharing link is created.
Eligible file changes across the connected Dropbox account. A selected folder prefix also includes nested folders, so use an isolated folder if you only want a narrow intake feed.
The prepared trigger and fixed subject group both kinds together. The notice shows the current file metadata; it does not label one as a new upload versus a revision.
Existing files are not backfilled and folder/deletion events do not send mail. Wait for Connected, then add or update a fictional file. Replaying a processed change can send another email.