Skip to content
OpenPhone logoGoogle Drive logo

Connect OpenPhone to Google Drive

Move data between OpenPhone 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.

OpenPhone triggers
5
OpenPhone actions
4
Google Drive triggers
3
Google Drive actions
17

Automation ideas

What you can build with OpenPhone and Google Drive

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

  • Call Recording Completed in OpenPhone creates Create new folder in Google Drive

    Fires when a call recording finishes. Useful for post-transcription or archival workflows.

  • New File in Google Drive creates Send Message in OpenPhone

    Trigger when a new file is uploaded.

  • Call Recording Completed in OpenPhone creates Create new file in Google Drive

    Fires when a call recording finishes. Useful for post-transcription or archival workflows.

  • New File in Google Drive creates Create Contact in OpenPhone

    Trigger when a new file is uploaded.

  • Call Recording Completed in OpenPhone creates Upload file in Google Drive

    Fires when a call recording finishes. Useful for post-transcription or archival workflows.

  • New File in Google Drive creates Update Contact in OpenPhone

    Trigger when a new file is uploaded.

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 OpenPhone 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.