This Zap creates a Oneflow contract whenever a deal's status stage changes to Negotiating in NetHunt CRM.
This streamlines CRM processes ensuring the timely creation of contracts.
1. Trigger: Updated opportunity stage in NetHuntCRM
App & Event
- Select NetHunt CRM as the App.
- Event: Select a specific event for the trigger. By default, this is set to New or Updated Record in filter (I.e. This means this Zap starts when a deal's status changes in NetHunt. You can select the trigger status in the Trigger stage.).
- Select your NetHunt CRM 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.
- Field: Select the field you want this trigger to be based on. By default, this is set to Stage (I.e. Run this Zap when the Stage of a Deal changes.)
- Search Query: Select which stage you want the trigger to be based on. By default, this is set to the Negotiating stage (I.e. Run this Zap when the Stage of a Deal enters the Negotiating stage).
- Folder: By default, this is set to Deals (I.e. Run this Zap when a Deal's stage changes.)
2. Action: Create contract in Oneflow
When the NetHunt opportunity reaches the stage defined in the filter, a contract is created in Oneflow.
- 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 set to get the Deal Name field from NetHunt. 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)
- 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.
3. Action: Find Record in NetHunt CRM.
- The objective of this stage is to choose a contact from NetHunt whom you wish to add as a participant to your Oneflow contract.
- Folder: By default, this is set to Contacts (I.e. Choose which folder within NetHunt to look for this contact).
- Record: By default, this is set to the Contact person field in NetHunt. Select which attribute of the contact you wish to search (I.e. Search for contacts by name, age, etc.)
- Search Query: Enter a search value based on the field you selected in the Record field.
- Should this step be considered a success when nothing is found: By default, this is set to No. If Yes is selected, the Zap can continue even without a Contact from NetHunt CRM. In this case, you'll have to manually add a Participant to the contract for the next action.
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.
- 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.
- Individual: Adds an individual 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 NetHunt.
- Participant name: By default, this field is mapped to the First Name field from the Deal in NetHunt. You may edit the participant's name or select the corresponding field in NetHunt.
- Participant email: By default, this field is mapped to the contact's email field from the Deal in NetHunt. You may enter a participant email of your choice or select the corresponding field in NetHunt.
- 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.
5. Action: Create comment in NetHunt CRM
- Folder: Select the NetHunt folder to create the comment in. By default, the Deals folder is selected.
- Record: By default, this is set to the NetHunt Deal from the trigger stage.
- Text: A default sample text for the comment is included along with a link to the Oneflow contract that was created via the Zap.
Once these steps are completed, you can publish the Zap. It's important to fill in all required fields in the Zap.