Template: Convert new Google Drive file into Oneflow contract (Zapier)

Christoffer Utterborn
Christoffer Utterborn
  • Updated

This Zap automatically creates a Oneflow contract whenever a Google document or PDF is uploaded to Google Drive.

NOTE

By default, this template supports Google Documents, Sheets, Slides, and PDFs.

1. Trigger: New file in Google Drive

This Zap starts when a new file is added to the specified Google Drive.

Choose account

  • Google Drive account: Select a Google Drive account from the dropdown.
    • You can choose from existing accounts connected to Zapier.
    • If the desired account isn't listed, click + Connect a new account to add one.

Set up trigger

  • Drive: Select a drive from your Google Drive account (personal or shared). You can also enter a drive name manually.
  • Folder: Choose the folder where files will be uploaded.
    • Navigate the folder tree in the dropdown.
    • If no folder is selected, files are uploaded to the root level of Google Drive.

2. Filter files in Google Drive

  • Only continue if...
    • File Extension: This filter checks the uploaded file type.
    • Allowed file types include:
      • PDFs
      • Google Docs documents
      • Google Sheets spreadsheets
      • Google Slides presentations
    • This Zap runs only if the uploaded file is one of the allowed types.

3. Action: Find a file in Google Drive

  • Click Continue to proceed (no additional input required).
    • The details of the uploaded file are retrieved once this step succeeds.

4. Action: Create contract in Oneflow

After identifying the uploaded file, a Oneflow contract is created automatically.

Choose account

  • Oneflow account: Select your connected Oneflow account.

Set up action

  • Create contract as: Select the Oneflow user who will create the contract.
    • The available Templates and Workspace options depend on the selected account.
  • Contract name: Defaults to the name of the uploaded document, followed by "Contract".
  • Workspace: Select the workspace where the contract will be created.
  • Template: Choose a template from your Oneflow account.

Data fields (optional)

NOTE

  • You can map values from the Google document to Oneflow data fields.
  • The selected template must belong to a template group that includes data fields created in Oneflow.
  • Learn more: Create a contract with data fields.
  • How many data fields to map: Enter 1–3 depending on your needs.
    • The corresponding fields will then appear below.
  • Custom ID of field n: Select the Oneflow data field from the dropdown.
  • Value of field n: Enter a value for the data field.

5. Action: Add attachment or Expanded PDF in Oneflow

This action attaches the uploaded file to the Oneflow contract.

NOTE

To upload a PDF to your Oneflow contract, the contract must include at least one attachment or expanded PDF section. Learn more: Attach documents or files.

  • Add attachment or Expanded PDF as: Choose who performs this action.
    • Contract creator (default): Adds the file as the contract creator.
    • Another Oneflow user: Adds the file as another Oneflow user.
  • File name: Defaults to the uploaded Google Drive file name.
  • File: Select the Google Drive file or paste its public link (max 20 MB).
  • Contract ID: Automatically populated from the previous contract creation step.
  • Upload as: Choose between Attachment (default) or Expanded PDF.

6. Action: Add participant in Oneflow

This step adds a participant to the contract.

  • Add new participant to contract as: Select who performs the action.
    • Contract creator (default): Adds the participant as the creator.
    • Another Oneflow user: Adds the participant as another Oneflow user.
  • Contract ID: Automatically fetched from the previous step.
  • Participant type: Choose the type of participant.
    • Individual (default): Adds an individual as a counterparty.
    • Colleague/Participant: Adds an owner-side party.
    • Company: Adds a company as a counterparty.

NOTE

The available fields vary depending on the selected participant type.

  • Party ID (if participant type is colleague): Enter a unique identifier for the organization.
  • Company name (if participant type is company): Enter the company name.
  • Participant name and email: Default to the connected Google Drive account's details (editable).
  • Role in contract:
    • Signatory (default): The participant must sign the contract.
    • Viewer: The participant can only view the contract.

7. Action: Send email in Gmail

This step sends the created contract via email.

  • Enter the details for the email to be sent.
  • To: Add up to five recipients, separated by commas.
  • Subject: A default subject is provided but can be edited.
  • Body: The body contains a default message with a link to the Oneflow contract.

NOTE

Once all steps are configured, publish the Zap to automate contract creation and delivery between Google Drive and Oneflow.

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request