Submit a ticket

Template: Create Oneflow contracts When Sellsy opportunity status changes

This Zap creates a Oneflow contract whenever an opportunity's status changes in Sellsy.

1. Trigger: Updated opportunity status in Sellsy

App & Event

  • Select Sellsy as the App.
  • Event: Select a specific event for the trigger. By default, this is set to Updated Opportunity Status (I.e. This means this Zap starts when an opportunity's status changes in Sellsy). 


  • Select a Sellsy account from the dropdown list. 
    • If the account you wish to link is not listed, then you'll need to add it to Zapier by clicking +Connect a new account.

2. Filter setup and testing

After an opportunity moves to another stage in the Sellsy pipeline, a filter is run to check the name of the stage. The workflow will continue only if the opportunity has reached the stage name you've specified in this filter.  

  • Status Label: Enter the new status label in this field.
    • You can customize the text field in this filter to match any stage in the Sellsy pipeline.
    • To do this, you'll need to know the name of the next status in the Sellsy pipeline (I.e. after the Sellsy opportunity stage changes).

3. Action: Create contract in Oneflow

When the Sellsy opportunity reaches the stage defined in the filter, a contract is created in Oneflow.

Choose account

  • Oneflow account: Select your Oneflow account from the list of connected accounts in Zapier.
    • If your Oneflow account is not listed, click on the  + Connect a new account button to add a new Oneflow account. To learn more, see Connecting to Oneflow accounts.


  • Create Contract as: Refers to the user creating the contract (I.e. Who is creating this contract?). Typically, the contract will be created by the Oneflow account user name you selected in the previous step.
    • Templates and Workspace options are populated based on the Oneflow account selected in this field.
  • Contract Name: By default, this field is mapped to the Opportunity Name field from Sellsy (from the trigger). However, you could customize the contract name to match your preference.
  • Workspace: Select the workspace from your Oneflow account to which this contract will be added to.
  • Template: Select a template from your Oneflow account.

Data fields (Optional)

  • You can assign values to data fields in Oneflow from fields in Sellsy.
  • To use data fields in a contract, the template group the contract belongs to needs to contain data fields (these are created in Oneflow).

  • To configure data fields for the Oneflow contract, make sure to select a template that belongs to a template group containing data fields.
  • To learn more about data fields, see Create a contract with data fields.

  • How many data fields do you need to map while creating the contract?: Once you've selected a template with data fields, enter the number of data fields you would like to configure in the text field that appears. (I.e. You may add up to three data fields to the Zap. Type 1, 2, or 3)
    • The specified number of data fields will then appear in the fields below.
  • Custom ID of field n: Select the Oneflow data field from the dropdown. This dropdown lists all data fields contained in the selected Template.
  • Value of field n: Enter a value for the Oneflow data field.

4. Action: Add Participant in Oneflow

This step involves adding a participant to the contract.

This template comes with pre-filled participant fields by default. If you need to modify the information in these fields, you are free to do so as you see fit. Alternatively, you can click Continue to proceed.
  • Add new participant to contract as: Select the user that's performing this action (i.e. who is adding the participant to the contract?).
    • Contract creator: add the participant as the contract creator (Oneflow user creating the contract).
    • Another user from Oneflow account: add the participant as another user in the Oneflow account.

  • Participant type: Select a participant type from the dropdown. 
    • Individual (Default): Adds an individual as a counterparty in the contract.
    • Colleague/Participant: Adds the participant as an owner-side party in the contract (i.e. For Instance, someone who works in the same organization as the contract creator can be added as a colleague in the contract.)
    • Company: Adds a company as a counterparty in the contract. 
      Note: The subsequent fields will change based on the participant type you select.
  • Party ID (if participant type is a colleague): Enter a unique identifier for the legal entity to which the participant (colleague) belongs to (i.e. For instance, this could be a company number). A party represents a legal entity in a contract.
  • Company name (if participant type is a company): Enter the company name or select the corresponding field in Sellsy.
  • Participant name: By default, this field is mapped to the Contact Full Name from the Sellsy opportunity. You may edit the participant's name or select the corresponding field in Sellsy.
  • Participant email: By default, this is mapped to the Contact email from Sellsy. You may edit the participant email or select the corresponding field in Sellsy.
  • Role in contract: Select a role in the contract for this participant.
    • Signatory: The participant will be required to sign the contract.
    • Viewer: The participant can only view the contract.


Depending on the template selected during the contract creation step, either the participant's email or their phone number on the contract can be mandatory at this stage.

5. Action: Create annotation in Sellsy

  • Linked Object Type: By default, this field is set to the Opportunity object from Sellsy.
  • Linked ID: By default, this field is mapped to the Opportunity ID from Sellsy (from the trigger stage).
  • Content: A default annotation content is included containing a link to the Oneflow contract. You may edit this message to match your preference.


Once these steps are completed, you can publish the Zap. It's important to fill in all required fields in the Zap.

Did you find it helpful? Yes No

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