Olmec Dynamics
H
·6 min read

How to Automatically Upload Files from Dropbox to Google Drive with Renaming and Slack Using Make.com

Automate Dropbox to Google Drive uploads with deterministic renaming and Slack alerts in Make.com, including collision handling and logging.

Introduction

If your team still moves files manually, the pain is predictable. A file lands in Dropbox, someone downloads it, renames it to match a convention, uploads it into Google Drive, then posts a Slack ping so the right person sees it. Miss one step and you get the same story every time, “I thought it was uploaded, why is it missing from the folder?”

This is a practical Cross-Platform Automation (XPA) build in Make.com that takes new files from Dropbox, computes a deterministic renamed filename, uploads them to Google Drive, then posts a Slack message with the final Drive filename. By the end, you will have a setup pattern you can adapt to any “incoming folder to system-of-record” workflow.

What You’ll Need

  • A Dropbox account with access to the folder where files arrive
  • A Google Workspace account with access to the destination Google Drive folder
  • A Slack workspace and a channel you want notifications in
  • A Make.com account with connections for Dropbox, Google Drive, and Slack
  • Permissions in Google Drive to upload into the destination folder

Assumptions for this simple run:

  • You are uploading files as-is, no document parsing or content transformation
  • You want one destination folder in Drive (or you can extend later with subfolders)

How It Works (The Logic)

When a new file appears in your Dropbox incoming folder, Make.com:

  1. reads the filename and extension from the Dropbox watcher output
  2. generates a final Drive filename using your renaming rules
  3. checks for filename collisions (optional but recommended)
  4. uploads the file to Google Drive using the computed final name
  5. posts a Slack message confirming what was uploaded (and where)
  6. optionally logs an audit row so you can investigate failures fast

Step-by-Step Setup

1) Choose your Dropbox “incoming” folder

Pick a single folder that represents “new work”. Example:

  • /Incoming/DeliveryDocs

In Make.com, create a new scenario and add the Dropbox watch trigger (the module name varies slightly by connector version, but the intent is “watch files”).

Set it to watch that exact folder, and ensure the trigger returns the file identifier plus at least:

  • original filename
  • extension (or you can derive it from the filename)
  • file id (or similar unique file reference)

Gotcha: if the folder already has lots of files, the scenario may backfill immediately. Start with an empty folder if possible.

2) Compute a deterministic renamed filename in Make.com

Add a Tools step that builds your finalName.

A good default naming pattern for ops workflows:

  • YYYY-MM-DD_originalFilename.ext

Inputs you will map from the trigger output:

  • originalFilename

Operations you apply:

  • derive today as YYYY-MM-DD
  • split originalFilename into base name and extension
  • compute finalName = today + '_' + base + ext

Also normalize illegal filename characters that can break expectations downstream. Common removals/replacements:

  • \\ / : * ? " < > |

3) Add collision handling (skip or version)

Decide your behavior:

Option A, skip duplicates

  • Use Google Drive to search for a file in the destination folder with the same finalName
  • Filter: only proceed if no matching file exists

Option B, version on conflict (recommended)

  • Search for existing files with finalName
  • If any exist, append a suffix such as __v2, __v3, etc.

For this simple build, versioning is usually easier for teams because it avoids “why didn’t it upload?” confusion.

4) Upload the file to Google Drive using the computed name

Add the Google Drive upload module.

Map:

  • File content: from the Dropbox file output (if the watcher only returns metadata, add a Dropbox “download file” step before upload)
  • Name: finalName
  • Parent folder: your destination Google Drive folder

Gotcha: some Dropbox watch outputs provide metadata but not the binary content. If Drive upload fails or uploads an empty file, you likely need the explicit Dropbox download module.

5) Post a Slack notification with the final Drive filename

Add a Slack post message module.

Send a short confirmation message, for example:

  • Uploaded to Google Drive: {{finalName}}
  • Original Dropbox file: {{originalFilename}}

If your Google Drive upload module returns a Drive file id, include it so your message can include a direct link later.

6) (Optional) Log an audit row to Google Sheets

For a simple ops workflow, add one lightweight log step.

Create a Google Sheet with columns like:

  • timestamp
  • dropbox_file_id
  • original_filename
  • final_name
  • drive_file_id (if available)
  • status (uploaded, versioned, skipped, failed)

When something goes wrong, this is the first place your team will check.

7) Test with real duplicates

Do two tests:

  1. upload Report.pdf once, confirm it lands in Drive as YYYY-MM-DD_Report.pdf
  2. upload Report.pdf again, confirm your collision logic kicks in (__v2 or skip)

Then confirm Slack received the message for both runs.

8) Turn it on and monitor first executions

After enabling the scenario:

  • check Make.com execution logs for upload failures or missing file content
  • confirm Slack permission for posting into the target channel
  • verify the Drive parent folder is correct

Real-World Business Scenario

A design and marketing team runs weekly client deliverable handoffs. Designers drop PDFs into Dropbox, and ops uploads them into client-specific Google Drive folders with consistent names. Previously, the workflow was manual, which meant duplicate names and “oops we uploaded the wrong version” issues.

After deploying this Dropbox to Google Drive renamed upload automation in Make.com, every file lands in Drive with a predictable date-prefixed filename. Slack notifications confirm uploads in the team channel, and the audit log makes it easy to trace what happened when someone expects a file and it is not there.

Common Variations

  1. Archive processed files in Dropbox

After a successful Drive upload, add a Dropbox action to move the original file to an archive folder like /Incoming/Archive. This prevents reprocessing.

  1. Parse project code from filenames

If your Dropbox filenames include a code like ACME_Proposal.pdf, extract it and rename as:

  • YYYY-MM-DD_ACME_Proposal.pdf
  1. Route to different Drive folders

If you have multiple destinations, add a simple Make.com router. Example rules:

  • filenames containing ClientA go to Drive folder A
  • filenames containing ClientB go to Drive folder B

Putting it all together

You built an operational Cross-Platform Automation (XPA) that watches a Dropbox incoming folder, computes a deterministic renamed filename, uploads to Google Drive, then posts to Slack. Optional logging turns the scenario into something your team can operate without guessing.

If you want this exact pattern tailored to your Dropbox folder layout, your Google Drive folder structure, and your naming rules, Olmec Dynamics builds automations for real businesses. You can also review how we approach XPA architectures in Cross-Platform Automation (XPA).