Introduction
GetAccept offers the ability for a GetAccept event that occurs for a Deal room or Contract to update a Microsoft Dynamics (MSD) property. What happens with your buyers in GetAccept can drive your Dynamics processes automatically. You can also layer CRM field conditions on top of GetAccept events, so updates only fire when both the GetAccept event and the conditions on the Dynamics record are met.
Example use cases:
Change Deal Stage in MSD based on Contract Signed
Change Deal Stage in MSD based on Contract rejected
Update Deal Stage or other MSD property based on Mutual Action Plan task or milestone completion
Update contact property based on visit to Deal room
When a contract is signed: IF CRM Stage = "Negotiation" AND Amount < $20,000 → set "Onboarding Type" = "Self-serve"; IF CRM Stage = "Negotiation" AND Amount ≥ $20,000 → set "Onboarding Type" = "Dedicated CSM"
When a proposal is opened by the buyer: IF Stage = "Proposal" AND Amount < $15,000 → set "Forecast Category" = "Pipeline"; IF Stage = "Proposal" AND Amount ≥ $15,000 → set "Forecast Category" = "Best Case"
Supported Events for Contracts
Signed by all
Signed by individual
Recalled
Rejected
Reviewed
Sealed
Sent
Expired
Supported Events for Deal Room
Visited
Viewed
Published
Unpublished
Deleted
Created
Task updated
Setup
This setup will guide you through how to configure an Event sync profile so that GetAccept events can update your Microsoft Dynamics properties. A profile will need to be created for every specific GetAccept event you want to use.
Prerequisites
Only GetAccept Enterprise customers have access to this capability.
You need to have installed the GetAccept integration (Details here) and to connect GetAccept to Microsoft Dynamics. Steps for connecting GetAccept to MSD below.
Log in to GetAccept
Click Settings in the right hand menu
Select Integrations
Click Connect below the option for Microsoft Dynamics
Enter the domain name for your MSD environment
Click Save
MSD is now connected and our Event Sync feature is enabled
Create a new Event Sync profile in the GetAccept Microsoft Dynamics Integration
Go to an object (e.g. Account or Opportunity) in your MSD environment where the GetAccept integration is enabled.
Open the GetAccept tab and log in to the integration with your GetAccept credentials
Note: You need to be an admin in GA
Click the menu in the top right of the integration
Select Settings
Select the Event sync tab
Click "Add new event sync profile"
Configure Event sync Profile
Set a name for the profile
Activate the profile if it should be used right away
Select the trigger conditions
Select Contract
Select the "Signed by all" event
Select the Dynamics entity to configure as Opportunity for this example
This is where you will be sending your document from in Dynamics with GetAccept
If you send contracts with GA from multiple places in Dynamics, create a separate profile for each main object
Click Continue
Select Dynamics object where you will update Dynamics properties with, in this case we have selected Opportunity
If you need to update multiple Dynamics objects, you will complete set up for the first object and then click on "Add new sync object"
Select the Dynamics property you want to update, in this case we have selected Sales Stage
Select "Update CRM Property" as the Action
Note: Selecting "Pull Data from GetAccept field" as the Action means that you will update the Dynamics property based on recipient filled data in GetAccept. Details here.
Select the "Property value" you want to update the Sales Stage to, in this case we have selected "Close"
For this Dynamics property, it is a dropdown and you will be able to select the exact deal stage you want. If the Dynamics property is a number type, or another type with pre set values, you will see that. If it is a free string field, you will be able to enter the desired input.
Click "Add new sync field" and follow steps 7i through 7k if additional GetAccept input fields are to be synced to Dynamics
Click Save
Add CRM field conditions to an Event sync profile
In addition to triggering on a GetAccept event, you can now require that one or more CRM field conditions are also true before the sync executes. This lets you build conditional logic that combines a GetAccept event with the live state of the Dynamics record, so the right field gets the right value based on real deal context.
When CRM field conditions are configured on a profile, GetAccept reads the live Dynamics record at the moment the event fires. The sync only executes when both the GetAccept event and the CRM conditions are met.
Typical examples include:
When a contract is signed: IF CRM Stage = "Negotiation" AND Amount < $20,000 → set "Onboarding Type" = "Self-serve"; IF CRM Stage = "Negotiation" AND Amount ≥ $20,000 → set "Onboarding Type" = "Dedicated CSM"
When a proposal is opened by the buyer: IF Stage = "Proposal" AND Amount < $15,000 → set "Forecast Category" = "Pipeline"; IF Stage = "Proposal" AND Amount ≥ $15,000 → set "Forecast Category" = "Best Case"
When a Deal Room is published: IF Stage = "Proposal" AND Amount < $25,000 → set "Deal Priority" = "Standard"; IF Stage = "Proposal" AND Amount ≥ $25,000 → set "Deal Priority" = "High"
For example, the two onboarding rules above are configured as two separate profiles on the same "Signed by all" event, each with its own Amount condition.
Note: CRM field conditions are an extension of event-based sync, not a replacement. Profiles without conditions continue to run on every matching GetAccept event. Add conditions only where you need the sync to behave differently based on the state of the Dynamics record.
Frequently asked questions
Can I set different rules for different deal sizes or stages?
Yes. Define separate Event sync profiles for each scenario, for example one profile for deals below a value threshold and another for deals at or above it, or different profiles per pipeline stage. Each profile evaluates its own CRM field conditions independently.
Does this replace the original event-based CRM sync?
No, it extends it. The original sync already triggers on a range of GetAccept events such as Mutual Action Plan task or milestone completion, buyer visits, and contract signatures. This release adds CRM properties (deal stage, deal value, or any CRM field) as additional conditions so the sync can make smarter decisions based on the actual state of the deal in Dynamics.
Who should configure CRM field conditions?
CRM admins and Revenue Operations teams configure the conditions in the GetAccept integration settings in Dynamics. Sales reps do not need to change their workflow; the impact is felt through cleaner CRM data and more reliable downstream automations.