Dropbox to Google Drive: Rename on Upload with Make.com and Slack

Introduction

Teams still move files manually from Dropbox to Google Drive, rename them to a convention, and ping Slack to confirm the transfer. Miss one step and you end up with naming collisions, misplaced files, or incomplete audit trails. This Make.com automation handles the flow for you: watch Dropbox for new files, rename them deterministically, upload to Google Drive, post a Slack notification, and optionally log the event for troubleshooting.

By the end of this post you will know the exact Make.com modules to use, how to build a safe de duplication flow, and how to verify the end to end process in production.

What You’ll Need

• A Dropbox account with a single incoming folder where files arrive
• A Google Drive folder where you want to store renamed uploads
• A Slack workspace channel for notifications
• A Make.com account with connections to Dropbox, Google Drive, and Slack
• Basic naming rules you want to apply, for example a date prefix and a sanitized base name

Note on prerequisites: you should have permission to read from Dropbox, write to Google Drive, and post to Slack from Make.com.

How It Works (The Logic)

When a new file appears in the Dropbox incoming folder, Make.com reads the file, computes a deterministic final filename, checks for collisions in Google Drive, uploads using the final name, posts a Slack alert with a link to the uploaded file, and optionally logs the event.

Trigger → Compute final name and collision check → Upload to Google Drive → Slack notification → Optional audit log

Step-by-Step Setup

1) Create a Dropbox watch trigger

• In Make.com, create a new Scenario and add the Dropbox module set to watch a specific incoming folder, such as /Incoming/Deliveries.
• Ensure the trigger returns at least: file_id, original_filename, and file_content or a download link if your scenario will fetch content before uploading.

2) Build a deterministic rename function

• Add a Tools module to derive a final file name. A practical pattern is: YYYYMMDD_originalfilename.ext
• Steps to compute:
  • Extract date = current date in your timezone
  • Split original filename into base and extension
  • Sanitize the base by removing illegal characters: \ / : * ? " < > |
  • Final name = date + "_" + sanitized_base + "." + extension

3) Collision handling in Google Drive

• Add Google Drive search to check if a file with finalName already exists in the destination folder.
• If a collision exists, apply a simple versioning approach by appending a counter, e.g. finalName__v2, finalName__v3, etc.
• If there is no collision, proceed to upload.

4) Upload to Google Drive

• Add Google Drive module: Upload a File.
• Map the file content from Dropbox (or use a direct Dropbox download step if necessary).
• Set the Target Folder in Google Drive and use finalName as the file name.

5) Slack notification

• Add Slack module to post a message in the chosen channel.
• Message template example: New file uploaded: {{finalName}}
  Source: Dropbox
  Original: {{originalFilename}}
  Drive link: <{{driveFileUrl}}|Open in Drive>

If the Make.com output includes a direct Google Drive share link, include it to make quick access easy for teammates.

6) Optional audit log

• Add Google Sheets or another log to record: timestamp, originalFilename, finalName, driveFileUrl, status (uploaded), and any error messages.

7) Test end to end

• Place a test file in Dropbox and verify the scenario creates a Google Drive file with the expected renamed name.
• Check the Slack channel for the notification and confirm the Drive link opens correctly.
• Review the audit log (if configured) for accuracy.

8) Turn on and monitor

• Enable the scenario and monitor the first 24 to 72 hours of runs.
• Look for errors such as permission issues, missing content, or naming collisions that were not handled by your versioning logic.

Real-World Business Scenario

A design studio receives weekly client deliverables via Dropbox. A simple Dropbox watch to Google Drive rename pipeline ensures every file lands in Drive with a consistent date-based name. Slack notifies the team so they know the latest asset is available and where to access it. An audit log helps finance and project managers confirm all client files are accounted for across systems.

If you want this built and tuned for your file flows, Olmec Dynamics builds these cross platform automations for real businesses. See what we do at Olmec Dynamics.

Common Variations

• Add an email alert to the uploader when the file is uploaded to Drive
• Extend to multi folder routing by detecting the file type or metadata and sending to different Drive folders
• Add content-based checks like a basic text extraction for auto tagging in Drive or Slack

Keeping file flows tidy

You now have a straightforward Make.com pattern that moves files from Dropbox to Google Drive with a deterministic rename, immediate Slack notification, and optional audit logging. If you want this integrated across your Dropbox, Drive, and Slack setup, Olmec Dynamics can implement and tailor these patterns for your team. Learn more at https://olmecdynamics.com.