Skip to content
ConnectUC logoGoogle Drive logo

Connect ConnectUC to Google Drive

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

ConnectUC triggers
8
ConnectUC actions
6
Google Drive triggers
3
Google Drive actions
17

Automation ideas

What you can build with ConnectUC and Google Drive

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

  • New Recording in ConnectUC creates Create new folder in Google Drive

    Triggers when a new call recording is available

  • New File in Google Drive creates Create Contact in ConnectUC

    Trigger when a new file is uploaded.

  • New Recording in ConnectUC creates Create new file in Google Drive

    Triggers when a new call recording is available

  • New File in Google Drive creates Set Do Not Disturb in ConnectUC

    Trigger when a new file is uploaded.

  • New Recording in ConnectUC creates Upload file in Google Drive

    Triggers when a new call recording is available

  • New File in Google Drive creates Find CDR in ConnectUC

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