Introduction
New: GetAccept has added new outcomes that can be set based on HubSpot data in addition to template selection. Learn more here.
Contact linking: automatically add the right contacts based on CRM conditions
File attachments: attach or exclude specific files based on deal type, region, or other CRM fields
Approver assignment: specify approvers conditionally (e.g., route deals above a discount threshold to a manager)
Expiry settings: apply different expiry rules depending on conditions
Integration visibility controls: show or hide the option to create Deal Rooms or contracts for specific conditions
As customers use our GetAccept integration more and more, it can raise challenges around template management for users:
What template should I use for a particular scenario
What templates should I not use
Where can I find the template
How can I get the information about all these templates that exist
Using the Conditional Setup feature allows an admin or manager to set rules as to when certain templates can and should be used. Remove the need to update your teams regarding your constantly growing content and let them focus on selling.
Use Cases
This tool is here to help you map your process, so can vary greatly how its used from company to company. But here are some examples of how it could be used. Here are a few examples:
If your users are sending from the Deal object, then consider setting up the conditions so that different templates are available for different Stages of the Deal.
Check what products have been added to a Deal. Maybe Deals with subscription products should use one template, and service products use another.
Maybe different teams or users should have different templates provided to them for different scenarios.
A combination of the above.
Create a new Conditional Setup profile in the GetAccept HubSpot Integration
Click Create on the GetAccept App card in HubSpot.
Note: The GetAccept integration is active from a HubSpot Deal, Contact, or Company.
Select Settings from the drop down.
Select "Conditional Setup" from the menu.
Click Add new conditional setup profile.
Set a Profile name and select the HubSpot sending object for the profile (e.g. Deal).
Create your first condition.
Select HubSpot Object where desired condition property is found. Can be the same as the sending object or a related object to it.
Select HubSpot object property. E.g. Deal Stage
Select Operator.
Select Property Value.
Optional: Click Add Property Conditions if you would like to add additional HubSpot properties for the HubSpot object selected in 6a.
Optional: Click Add a new condition group if you would like to have other conditions based on HubSpot properties from different objects than used in Step 6.
Additional condition groups would operate with And logic, so all conditions must apply for desired output.
Select one of two outcomes based on configured conditions
Click Add conditional rules to suggest or filter Deal Room or contract templates, set GetAccept visibility options, add files as attachments, add contacts, and/or to set expiry days.
Click Add Sub Case to create nested logic for more complex use cases. Logic for this is the same as in step 6.
When you've clicked Add conditional rules, you can choose the outcome you want, in this example we will select Template selection configuration, you may then select either the option to Filter or Suggest GetAccept templates.
Filter will show only those GetAccept Templates selected
Suggest will show the suggested template at the top of the integration when creating a deal room or contract.
Select desired templates for Deal Room and Contracts.
Note: If no templates are selected for the filter option for Deal Room or Contracts, those options will be hidden in the integration when the applied conditions exist.
Click Save.
Test the scenario configured.
Notes: How conditional logic works
Only one profile per Object per GetAccept Entity
Branches are evaluated in order from top to bottom. The first branch that matches the conditions of the object will be selected.
Default branches do not have conditions. These branches are last in the running order and should be used as an ‘ELSE’ function when no preceding branch evaluates to true
Note: If no templates are selected for the filter option for Deal Room or Contracts, those options will be hidden in the integration when the applied conditions exist.