What Pipedrive CRM Data Can Be Synced?

What Objects and Actions Are Supported?

Object	Formstack Sync Object Name	Permissions	Custom Field Support	Relationships*	Required Fields**
User	Owner	Read	Yes	---
Person	Contact	Read / Update / Create	Yes	User Company Deal	First Name Last Name Email
Organization	Company	Read / Update / Create	Yes	Person Deal User	Company Name
Deal	Opportunity	Read / Update	Yes	Person Company User	Name Expected Close
Activity	Activity	Read / Create	Yes	Person Company Opportunity User	Title Marked as Done Time

* Relationships can be used to map fields from related Objects.

* Where a 1-to-Many relationship exists between related objects, we do not recommend mapping fields.

** Required fields must be mapped in Formstack Sync in order for records to sync as expected. Learn more about how to best manage required fields here.

Important Functionality Notes

Object	Important Notes
Acitivty	Marked as Done is the field used to deduplicate with the other systems "Occurred At" field for Activities Only Closed Activities will sync out to another system Must have Contact Relationship configured and set in the order from source system to destination system Type does not have to be mapped but if you do, the default value must be either BLANK or set to one of the available types (Call; Meeting; Task; Deadline; Email; Lunch)
Deal	Must have close dated ASSIGNED in order for the Deal to be paired up with another opportunity-type record in another system.
Person	There is an owner_id field on the Person (Contact) record that can be updated via API. If a customer is trying to assign an owner from a paired system, they must map to the owner_id field AND must use the exact Owner ID of an existing Pipedrive user. Person > Owner Name field is the Full Name of the Owner. It is not split up between First and Last Name and you can not split up this full name when syncing to the other system.

Now that you know what type of data you can sync, time to start mapping your fields. Click here to learn how to get started on mapping your data.