Automate GetAccept workflows based on Salesforce data

Optimize your sales workflow by using Salesforce data to automate Deal Room and Contract creation in GetAccept.

April 23, 2026

Introduction

As sales processes grow in complexity, manual document configuration can lead to errors and delays. The Conditional Setup feature allows administrators to move beyond simple template suggestions and create a fully automated "Automation Engine" within Salesforce. By defining rules based on Salesforce record data, you can control exactly what your users see and automate the tedious parts of document preparation.

Key Automation Capabilities

This update expands the "THEN" logic of your conditional profiles, allowing you to automate the following five areas in addition to the ability to select/filter GetAccept templates:

• Filter or suggest GetAccept templates based on Salesforce data so your end users use the right template every time, with no mistakes or wasted time. More details here.

• Create Options: Dynamically show or hide the ability to create a Contract, Non-signable document, or Deal Room based on specific Salesforce criteria.

• Attach Files: Automatically pull Salesforce Files or Attachments from the record directly into your GetAccept document package.

• Pre-populate Contacts: Intelligently map recipients from Salesforce (via Contact Roles, Lookups, or static users) to specific GetAccept or Template roles.

• Send / Publish Options: Control the user interface by enabling or disabling specific action buttons like "Sign and Share Link" or "Publish."

• Additional Settings: Automatically set document parameters such as Expiry Dates.

Setup Guide

(Pre-requisites: Ensure that you have our GetAccept integration Version 2.132.0 or higher and that you have the GetAccept_Integration_Admin permission set assigned)

This setup will guide you through creating a Conditional profile.

1. Navigate to the GetAccept Admin App | Conditional Setup

2. Click Create profile

3. Search and select the object you wish to set up the profile for and click Create

At this point a new Profile has been created for you. If you cancel, nothing will be saved. The profile has set up the basics needed for the profile to work well:

• It is automatically assigned to the first GetAccept entity it can find.
  • It's been given a standard name and description which you can edit for your own organization.
  • The entry condition for the profile is set to Sending Object = ‘Account’, or whatever object you have selected when creating the profile.
  • Then it has also created two branches to get you started. Case 1 - you can begin setting your conditions here. Default Case - this is the fallback branch where conditions cannot be set.

So let's continue to set up the profile.

1. Navigate to Case 1 and set the conditions as you wish within the IF card. You can set multiple.

2. Next you can decide what you wish to happen in the THEN card. Click Select presets.

3. Set the outcomes for the if conditions as desired. A detailed example of template selection can be referenced here.

4. Click back into the primary object in the overview panel. On the edit panel on the right you can create further branches. In each of these branches you can repeat the same steps as above for every other scenario you’re interested in solving.

5. When all your specific branches have been created. You can finally decide what happens when none of those branches evaluate to true. This can be done by editing the THEN card within the Default Case. Here you have the same possibilities. Either create sub-branches or select the standard default templates you wish to be used.

6. When you are finished, you can hit Save. You can also use the test feature in the dropdown in the top left to see how the conditions work for a specific record.

7. When you’re ready for the profile to be active for your users, click the activate toggle.

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.
• Profiles can be comprehensive in size and complexity, but there is a limitation of approximately 100 outcomes. (may increase in future)