Submit a ticket

Template: Convert new Dropbox PDF file into Oneflow contract

This template can be used to create Zaps that automates the process of creating Oneflow contracts upon uploading files to a connected Dropbox account. 

Once a Zap is created from this template, the following actions and triggers will be visible.

New File in Dropbox

This Zap will start off when a new file is uploaded to the chosen Dropbox account. 

  • The user is required to select a Dropbox account of their choice.
  • A list of already connected Dropbox accounts in the logged in Zapier account will be available to choose from. 
  • If the required account is not available in the dropdown list, click on the “+ Connect a new account” button to add a new Dropbox account.


  • Once the required account is selected, the user has the option to choose a folder where to look for a file upload.
  • The list of top-level folders available in the connected Dropbox account at first, the user can navigate inside the folders by clicking the dropdown next to each folder name.
  • Furthermore, the user can opt to choose to include file objects,so that no errors will be provided when a file greater than 100MB is uploaded to the selected Dropbox storage account.

Filter files in the Dropbox account

Next a filter action is added to the Zap, to continue execution only if the specified conditions are met. 

  • The condition here is to check if the extension of the uploaded file is PDF.
  • Which means, this zap executes only if the uploaded file is a PDF. Users have the option to add or change the filter options to choose files upon different criteria.


Create Contract in Oneflow

Having picked the necessary files, now the Oneflow contract can be created. In this step, the Create Contract action will be executed with the chosen Oneflow account, whom the contract is created as.

  • The user can connect a new Oneflow account in the instance where the Oneflow account of the contract creator is not listed in the dropdown.
  • The name of the contract is set to be taken from the uploaded document, with the prefix Contract.
  • The user has the liberty to select a workspace and a template of their choice to be used for contract creation.


  • When a user wants to transfer any data from the uploaded document to the Oneflow contract that is going to be created, ‘data-fields’ can be used. 
  • To be able to use data fields in a contract, a template group with data fields needs to be created in Oneflow end.
  • Read more on how to create a template group and add data fields. Once such a template is created, that can be used to transfer data from the file to the Oneflow contract easily.

Add an Attachment or Expanded PDF in Oneflow 

  • An attachment can be added to the same contract with this action.
  • The user has to select the Oneflow account of the user.
  • By default the expanded PDF option is set as the option for the ‘upload as’ dropdown (attachment/expanded PDF), therefore the file will be added to the contract as an attachment.
  • The file name is set to be the name of the uploaded file and the file will be the uploaded file itself. 
  • The Contract Id is set to be taken from the previous contract creation action’s output. 
  • Provide a publicly downloadable URL of the required file that does not exceed 20MB in size, however the selected template of the contract should have exactly one attachment/expanded PDF section for the user to be able to upload any files without a failure.
  • By default the file will be uploaded to the contract as an attachment.

Add Participant in Oneflow 

  • The new participant will be added to the contract as the contract creator by default (the user has the ability to change the option).
  • The contract id is set to be taken from the previous contract creation action 
  • The participant type is set to be added as an individual by default, but the user has the liberty to change the participant type as required.
  • The other fields related to the participant, such as the participant name, email and contact number have to be filled by the user accordingly.
  • The role of the participant in the contract is selected as signatory as default role. 


Send Outbound Email

  • This action is for sending the created contract via email.
  • Users can add the necessary details to send the email successfully, can be provided while setting up the action or can be selected from the previous actions of the zap. 
  • The details such as the subject and email body are set by default.


Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.