Capturing Recipient Filled Data in Pipedrive | GetAccept Help Center
Capturing Recipient Filled Data in Pipedrive
We've made it easier to let your recipients fill in data in a GetAccept document and have that data saved back where you need in Pipedrive.
April 23, 2026
Overview
Introduction
GetAccept offers the ability for a recipient of a document to fill in data in added text field boxes that you add to a template. You may now capture this recipient-filled data, on signing, and process it back in Pipedrive exactly the way you need. As a result, it is now possible for recipients to update their own records in Pipedrive under your supervision. This feature works with both scenarios:
- Text fields placed on a PDF template
- Form fields inserted within an editor block
Setup and Configuration
Setup
Pre-requisites: Ensure that you have our GetAccept Pipedrive Chrome extension Version 1.15 or higher.
This setup will guide you through how to configure an Event Sync profile so that your recipient-filled data from the GetAccept document populates the correct Pipedrive fields upon document signing.
Building Event Sync profiles for how GetAccept filled fields map to Pipedrive fields automatically
Create a new Event Sync profile in the GetAccept Pipedrive Integration
a. Log in to the GetAccept Pipedrive integration.
b. Select the drop-down menu in the top right of the integration.
c. Select "Advanced Settings". Note: This is only available to GetAccept Admin users.
d. Select the tab named "Event Sync".
e. 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
- Collecting Recipient filled data with a Deal Room is currently not supported.
- Select the "**Signed by all" event
- Select the Pipedrive main object as Person, Organization, 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 with recipient filled data, in this case we have selected Deal
- If you need to update multiple Pipedrive objects, you will complete setup 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 Value
- Select "Pull data from GetAccept" as the Action
- Note: Selecting "Update CRM property" as the Action means that you will update the Pipedrive property directly and not based on filled data in GetAccept
- Enter the field name (label), in our case VAT Number, from your GetAccept template that will be filled with data that will be synced back to Pipedrive
- 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
Test the Event sync profile
- Send a GetAccept contract from a Pipedrive Person, Organization, or Deal that has an event sync profile configured
- Return to the Event sync profile page
- Select the Event sync profile configured in step 2
- Click test
- Enter the document id sent in step 3a
- When you open the send document as the recipient, the document id will be in the url as shown in the below example in bold (e.g. ttps://test.getaccept.com/v/xj5xtsv829x3/2e95dr2v8y2vek/a/aw851d736d9918e8b6421b7610883re7
- Validate that all fields have successfully been updated in Pipedrive
Note: For steps 3b to 3f, you could also sign the contract yourself after making the send in 3a and validate manually in Pipedrive if the fields were updated.
Limitations
Limitations
- Currently, we cannot update Pipedrive dropdown fields;
- Currently not supporting Pipedrive date fields; this will be supported in 2025.
- Manual triggering of a data sync is only possible from the Event sync profile; this will be added to the document analytics view in the integration in a future release.