Skip to content
Box logoGoogle Drive logo

Connect Box to Google Drive

Move data between Box and Google Drive the moment it happens. Build the flow visually, or let AI write it for you, then run it on our cloud or your own infrastructure.

Box triggers
3
Box actions
1
Google Drive triggers
3
Google Drive actions
17

Automation ideas

What you can build with Box and Google Drive

A few flows teams run between Box and Google Drive. Use one as a starting point, or build your own from scratch.

  • New File in Box creates Create new folder in Google Drive

    Triggers when a file is uploaded

  • New File in Google Drive creates Custom API Call in Box

    Trigger when a new file is uploaded.

  • New File in Box creates Create new file in Google Drive

    Triggers when a file is uploaded

  • New Folder in Google Drive creates Custom API Call in Box

    Trigger when a new folder is created or uploaded.

  • New File in Box creates Upload file in Google Drive

    Triggers when a file is uploaded

  • New or Updated File in Google Drive creates Custom API Call in Box

    Trigger when a file is created or updated, checked on a schedule. Each event carries a Change Type of created or updated, and several edits between two checks arrive as a single event. Renaming a file counts as an update. Trashing a file is not an event, and neither is restoring one from the bin nor moving an existing file into the watched folder. Selecting a parent folder watches its direct children only, not sub-folders.

Questions, answered

No. Pick a trigger on either piece and an action on the other, map the fields, and turn the flow on. Add a code step later only if you want to.

Yes. Build one flow that starts in Box and acts in Google Drive, and a second that runs the other way, in the same project.

On our EU cloud in Frankfurt, or self-hosted on your own infrastructure with Docker or Kubernetes. The MIT-licensed core means there is always an exit.