Introduction
GetAccept offers the ability for a GetAccept event that occurs for a Deal room or Contract to update a Pipedrive property. What happens with your buyers in GetAccept can drive your Pipedrive processes automatically.
You can also layer CRM data conditions on top of GetAccept events so the sync only fires when both the event and the Pipedrive field values match your rules. This lets you build conditional logic that adapts to deal context, such as deal stage or deal value.
Example use cases:
Change Deal Stage in Pipedrive based on Contract Signed
Change Deal Stage in Pipedrive based on Contract rejected
Update Deal Stage or other Pipedrive property based on Mutual Action Plan task or milestone completion
Update contact property based on visit to Deal room
When a GetAccept contract is signed: IF Stage = "Negotiation" AND Amount < $5,000, set "Onboarding Type" = "Self-serve"; IF Stage = "Negotiation" AND Amount ≥ $5,000, set "Onboarding Type" = "Dedicated CSM"
When a GetAccept 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 Pipedrive properties. A profile will need to be created for every specific GetAccept event you want to use.
Create a new Event Sync profile in the GetAccept Pipedrive Integration
Create a new Event Sync profile in the GetAccept Pipedrive Integration
Log in to the GetAccept Pipedrive integration.
Select the drop-down menu in the top right of the integration.
Note: The GetAccept integration is active from a Pipedrive Deal, Person, or Organization.
Select the tab named "Event sync"
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 "Sent" event
Select the Pipedrive main object as Contact, Company, or Deal
This is where you will be sending your document from in Pipedrive with GetAccept
If you send contracts with GA from multiple places in Pipedrive, create a separate profile for each main object
Click Continue
Select Pipedrive object where you will update Pipedrive properties, in this case we have selected Deal
If you need to update multiple Pipedrive objects, you will complete set up for the first object and then click on "Add new sync object"
Select the Pipedrive property you want to update, in this case we have selected Deal Stage
Select "Update CRM property" as the Action
Note: Selecting "Pull Data from GetAccept field" as the Action means that you will update the Pipedrive property based on recipient filled data in GetAccept
Select the "Property value" you want to update the Deal Stage to, in this case we have selected "Proposal made"
For this Pipedrive property, it is a dropdown and you will be able to select the exact deal stage you want. If the Pipedrive 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 2i through 2k if additional GetAccept input fields are to be synced to Pipedrive
Click Continue
Enable Product sync toggle if you want optional or variable products updated in GetAccept to update Pipedrive product line items
Click Save
Add CRM field conditions to a sync profile
Event sync profiles can include conditions based on Pipedrive field values, so the profile only updates a property when both the GetAccept event fires and the CRM data matches your rules. This is useful when you want different outcomes depending on the deal context, such as deal value or deal stage.
When the event fires, GetAccept reads the live Pipedrive record and applies the update only if every condition is met.
Example conditional rules
You can combine GetAccept events with Pipedrive field values to express logic like the following:
When a GetAccept contract is signed:
IF Stage = "Negotiation" AND Amount < $5,000, set "Onboarding Type" = "Self-serve"
IF Stage = "Negotiation" AND Amount ≥ $5,000, set "Onboarding Type" = "Dedicated CSM"
When a GetAccept 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 GetAccept 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"
FAQ
Does this replace the original event-based CRM sync?
No, it extends it. The original sync already triggers on a range of GetAccept events. This release adds Pipedrive field conditions (deal stage, deal value, or any CRM field) so the sync can make smarter decisions based on the actual state of the deal in Pipedrive.
Who should set up the conditional rules?
CRM admins and Revenue Operations teams configure the conditions in the GetAccept integration settings. Sales reps do not need to do anything differently.
Can I set different rules for different deal sizes or stages?
Yes. You can define separate conditions for deals above or below a value threshold, for different pipeline stages, or combinations of Pipedrive fields.
Is this feature available on my plan?
CRM field conditions are included on the Professional and Enterprise plans. The feature is not included on the E-sign plan, Web trial, or Sales trial.