Submit a ticket
Welcome
Login

Getting started with Power Automate

The primary use case of the Power Automate connector is a simple flow where you can create a contract, add participants, and send it to them. In this article, we will build a contact-creating flow triggered by a SharePoint event. 

Set up a new connection

Before creating a contract, we will set up a trigger for it:

Now to the flow setup:

  1. Click New step and search for Oneflow.
  2. On the Actions tab, click the Create a contract action.
  3. In the Oneflow window that appears, specify the Connection name, user email address, and the API key to the integration extension that you can find here.

Create a flow

Now you can start creating an automatic flow. In our case, we'll consider a basic four-step flow: 

  • Create a contract
  • Add a participant
  • Add an attachment
  • Publish the contract.

Create a contract

Here's what you need to do to create a new contract flow using the Create a contract action:

  1. In your flow, click New step, and on the Actions tab, select Create a contract action.
  2. In the action window, fill in the Workspace name, Template name, and the Contract name (optionally).
  • Workspace name: The name of a workspace in which your contract will be created.

  • Template name: The template from which you want to create your contract.

  • Contract name: Input the name of your contract (optional).

      

        3. You can also populate data fields during contract creation: 


By clicking on the dropdown in the first field, select a data field to populate, and insert a value in the Data field Value field.

            


Note:

This action will only show workspaces and templates available to the user whose email you used to create the connection.

Add participants

Once your contract is created, you can add participants. Let's create the next step in our flow:

  1. Click the New step button.
  2. Go to the Actions tab and click the Add Participant action.
  3. In the Add Participant window, fill in all required fields.

    Note:

    If you decide to fill in the Party Country Code, ensure it contains only an ISO code. Otherwise, an error will occur.

    You can add three types of participants to your contracts, and depending on the type you choose, the input fields for this action will change:

    - Company: a participant who is associated with a counterparty
    - Individual: a participant who represents themselves
    - Ownerside: a participant who is a member of your team. will be automatically added to your owner-side party.

Note:

Field requirement is dynamic for this action, depending on the fields and values you select. Please refer to our API documentation to better understand participant and party models.

Suppose you want to add multiple participants under the same Company-type party. The action will try to automatically match it with an already created one by comparing fields like Party name, Party country code, and Party identification number. As long as you fill in the same party data in multiple action steps, Company type participants will end up in the same party.

Upload attachments

You can add attachments to your contract, like an expanded PDF or just an attached file using the Upload attachments action.

  1. Click the New step button.
  2. Go to the Actions tab and click the Upload attachments action.
  3. In the Upload Attachments window, fill in all required fields:
    - Contract Id: ID of the contract you want to publish. It can be found as an output for the Create a Contract action.
    - File: the body of the file that is attached. Only byte array format is supported; base64 encoded string will not work, so you must first use the base64ToBinary function in the flow to transform your base64 string.
    - File (file name): name of the file. It should always come with the file extension. Example: quotedetails.pdf. The system will throw an error if the file name does not contain an extension.
    - Upload As: select attachment is a regular file attachment in your contract, while expanded_pdf displays your PDF document's content in the contract's PDF section.

Note:

Only one PDF section is allowed for a contract. If the contract does not have an attachment section, but you try to upload an attachment, the system will throw an error. The same goes for expanded PDFs.


Set Data Field values

You can set Data Field(s) values for existing contracts too. You can read more about data fields in a separate article - Data fields


  1. Click the New step button.
  2. Go to the Actions tab and click the Update a data field action.
  3. In the Update a data field window, fill in all required fields:
    - Contract Id: ID of the contract you want to publish. It can be found as an output for the Create a Contract action.
    - Custom id: custom id of the data field you want to update. custom id are equal to external-key of the data field. You can find them in template group settings in your Oneflow account.
    - Value: Value you want to set for the data field in question.

Note:

Templates without a template group don't have data fields. Please make sure your template belongs to a template group if you want to use this action.

Publish a contract

If you feel your contract is ready for signature after completing the previous steps, you can use the Publish a contract step to send it to all recipients.

  1. Click the New step button.
  2. Go to the Actions tab and click the Publish a contract action.
  3. In the Publish a contract window, fill in all required fields.
    - Contract Id: ID of the contract you want to publish. It can be found as an output for the Create a contract action. 
    - Subject: 
    the subject of the message that Oneflow will send to participants. 
    - Message: 
    the message body of the notification.

Note:

If delivery channel = 'sms', the system will send an SMS message to them. The system will send an email message if the delivery channel =''emai'' respectively.

Upcoming features

We are working on enabling triggering additional flows in the future. You will be able to trigger additional flows when a contract is signed, declined, a participant visited a contract, etc. 

Did you find it helpful? Yes No

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