Skip to content

Google Drive

Every attachment in the right Drive folder

Stop downloading and re-uploading. Workflows create the client’s folder if it does not exist yet and drop the attachments into it — or a text file you write from the email.

Connection
OAuth sign-in
Actions
3
One folder per client, created on the fly Hover a node to see its role · Drag to move the graph
Email receivedEmail receivedEmail receivedExtractExtractExtractModelDrive — create a folderDrive — create a folderDrive — create a folderDrive — upload a fileDrive — upload a fileDrive — upload a file
One folder per client, created on the fly

What you can automate with Google Drive

Actions

What a workflow can do next.

  • Drive — upload a file

    Uploads the attachments (from the email or added by a step), or a text file you write, into a Google Drive folder.

  • Drive — search files

    Searches files in Google Drive and puts the list into the working data.

  • Drive — create a folder

    Creates a Google Drive folder unless one with the same name already exists under the same parent, and returns its id for the rest of the workflow.

Workflows you can build

Each one starts from a real situation and uses only nodes that exist today. Test it on past emails before you publish it.

  • One folder per client, created on the fly

    The client’s folder is created unless it already exists, and the email’s attachments are uploaded into it.

    1. Email received
    2. Extract
    3. Drive — create a folder
    4. Drive — upload a file
  • Keep signed contracts together

    Emails recognised as signed contracts have their PDF saved to the Contracts folder, the rest is left alone.

    1. Email received
    2. Categorize
    3. Drive — upload a file
  • Check before you store

    A search tells the workflow whether the document is already in Drive; only new files are uploaded.

    1. Email received
    2. Drive — search files
    3. Condition (If)
    4. Drive — upload a file

How to connect Google Drive

Drive is a separate access on your Google connection: one click on Connect Google Drive, one consent, and the Drive nodes can use it.

Before you start

  • A Google account already connected to Loop & Roll.
  • The Google Drive access granted on that account.

The full guide in the documentation

  1. An administrator of your Loop & Roll instance registers your organisation’s Google OAuth application once, in a Google Cloud project.
  2. Each member opens Connections, clicks Add a connection, then Connect on the Google card, and accepts the consent screen.
  3. On the account’s row in Connections, click Connect Google Drive: a separate consent, for that access only.
  4. Pick the account in the node: the workflow acts with that member’s own rights.

Automate Google Drive with Loop & Roll

We build the workflow around your processes, test it on your past emails and put it into service with your teams.