Skip to main content

Default CRM Fields for Databook Salesforce Integration Sync

List of fields to support key use cases and capabilities unlocked by the Salesforce integration

Written by Alex

Overview

By default, the integration syncs selected standard fields relating to standard objects such as accounts and opportunities, to support enhanced analytics, agents and AI-generated assets in Databook.The integration is designed to provide Salesforce admins with full control, deciding which data point can be synced.

This list is a starting point for the CRM sync: to support more complex workflows, we will need to work with your team to identify additional custom fields and objects that provide relevant context for the workflow.

Read-only vs write access

We only require read access to the majority of fields that we sync. However to support the GTM Decision System, we require create or update access to certain fields.

The specific fields were we require additional access (create or update) are listed separately for each object. We take the following approach to fields with write access:

  • Writes are limited to the specific fields listed below

  • Writes are always user-initiated

  • Every push is recorded in an audit log capturing who changed what, the before and after values, and whether Salesforce accepted the change

  • Salesforce validation rules and duplicate rules remain fully in force; when a validation rule rejects a change, the app surfaces the rule to the user rather than bypassing it

  • We do not request delete access for any fields


Object: Account

Read-only fields

  • Account Source

  • Annual Revenue

  • Billing Country

  • Billing Country Code

  • Billing State

  • Billing State Code

  • Created At Date

  • Description

  • DUNS Number

  • ID

  • Industry

  • Is Deleted

  • Is Partner

  • Is Person Account

  • Last Activity Date

  • Last Modified Date

  • Name

  • Number Of Employees

  • Owner ID

  • Ownership

  • Parent ID

  • Ticker Symbol

  • Type

  • Website

Write fields

Field

Access

Purpose

Name

Create

Create the account only when no match exists

Notes

DUNS numbers

Databook strongly recommends syncing the DUNS Number for a given Account, so that we can accurately map Salesforce accounts to companies in Databook.

This object and these fields have been identified to support all guided workflows and reasoning where an understanding of the current context in an Account is important.


Object: Contact

Read-only fields

  • Account ID

  • Buyer Attributes

  • Contact Source

  • Created At Date

  • Department Group

  • Description

  • Do Not Call

  • Email

  • First Call Date Time

  • First Email Date Time

  • First Name

  • Has Opted Out Of Email

  • ID

  • Is Person Account

  • Is Priority Record

  • Last Activity Date

  • Last Modified Date

  • Last Modified By ID

  • Last Name

  • Lead Source

  • Owner ID

  • Title

  • Title Type

This object and these fields support workflows where an understanding of the Contact is important, such as Prospecting and Account Planning.

Write fields

Field

Access

Purpose

Account ID

Create

Prefer the contact on the matching account; set the account on new contacts

Email

Create

New contact created from a meeting attendee

First Name

Create

New contact created from a meeting attendee

Last Name

Create

New contact created from a meeting attendee

Title

Create

Role context on the new contact

Object: Event

Read-only fields

  • Account ID

  • Activity Date

  • Activity Date Time

  • Created At Date

  • Description

  • Duration In Minutes

  • End Date Time

  • Event Subtype

  • ID

  • Is All Day Event

  • Is Deleted

  • Last Modified Date

  • Owner ID

  • Start Date Time

  • Subject

  • Type

  • Location

  • Who ID

  • What ID


Object: Lead

Read-only fields

  • Annual Revenue

  • Company

  • Company DUNS Number

  • Converted Account ID

  • Converted Contact ID

  • Converted Opportunity ID

  • Converted Date

  • Country

  • Country Code

  • Created At Date

  • Currency ISO Code

  • Description

  • Email

  • First Call Date Time

  • First Email Date Time

  • First Name

  • Has Opted Out of Email

  • ID

  • Is Converted

  • Is Deleted

  • Last Activity Date

  • Last Name

  • Lead Source

  • Owner ID

  • Phone

  • State

  • State Code

  • Status

  • Title

  • Website

Write fields

Field

Access

Purpose

Company

Create, Update

Adding or updating leads captured in GTM Decision System

Email

Create, Update

Adding or updating leads captured in GTM Decision System

First Name

Create, Update

Adding or updating leads captured in GTM Decision System

Last Name

Create, Update

Adding or updating leads captured in GTM Decision System

Lead Source

Create, Update

Adding or updating leads captured in GTM Decision System

Phone

Create, Update

Adding or updating leads captured in GTM Decision System

Title

Create, Update

Adding or updating leads captured in GTM Decision System

Website

Create, Update

Adding or updating leads captured in GTM Decision System


Object: Opportunity

Read-only fields

  • Account ID

  • Age In Days

  • Amount

  • Close Date

  • Contact ID

  • Created At Date

  • Currency Iso Code

  • Description

  • Fiscal

  • Fiscal Quarter

  • Fiscal Year

  • Has Open Activity

  • ID

  • Is Closed

  • Is Deleted

  • Is Won

  • Last Activity Date

  • Last Activity in Days

  • Last Modified Date

  • Last Stage Change Date

  • Last Stage Change In Days

  • Lead Source

  • Name

  • Next Step

  • Owner ID

  • Probability

  • Stage Name

  • Type

Write fields

Field

Access

Purpose

Name

Create, Update

Update or create opportunity from GTM Decision System

Account ID

Create, Update

Update or create opportunity from GTM Decision System

Amount

Create, Update

Update or create opportunity from GTM Decision System

Close Date

Create, Update

Update or create opportunity from GTM Decision System

Stage Name

Create, Update

Update or create opportunity from GTM Decision System

Owner ID

Update

Update or create opportunity from GTM Decision System

Next Step

Create, Update

Update or create opportunity from GTM Decision System

Notes

Opportunity amounts and currencies

If your CRM contains opportunities with amounts in different currencies, we also need to sync a currency field for each opportunity, plus a normalized amount field for each opportunity that converts the value of the opportunity amount into the primary currency your organization uses (e.g. USD, EUR, GBP).

Next steps

If there are custom fields capturing next steps in more detail, or a history of next steps for the deal, these would be relevant also to sync.

This object and these fields support guided workflows where an understanding of the Account and associated Opportunities is important.


Object: OpportunityStage

Read-only fields

  • API Name

  • Created At Date

  • ID

  • Is Active

  • Is Closed

  • Is Won

  • Last Modified Date

  • Sort Order

This object and these fields provide stage progression information for workflows like Deal Coaching.

Write fields

Field

Access

Purpose

Contact ID

Create

Meeting attendee added to (new) opportunity

Is Primary

Create

Meeting attendee added to (new) opportunity

Opportunity ID

Update

Meeting attendee added to (new) opportunity

Role

Create, Update

Meeting attendee added to (new) opportunity


Object: OpportunityContactRole

Read-only fields

  • Contact ID

  • Currency Iso Code

  • Division

  • ID

  • Is Deleted

  • Is Primary

  • Opportunity Id


Object: OpportunityHistory

Read-only fields

  • Amount

  • Created At Date

  • Close Date

  • ID

  • Is Deleted

  • Opportunity ID

  • Probability

  • Stage Name

This object and these fields are identified to support workflows like Solution Positioning or Deal Coaching where historical deal context is important.


Object: Task

Read-only fields

  • Account ID

  • Activity Date

  • Call Type

  • Call Duration In Seconds

  • Created At Date

  • Description

  • ID

  • Is Closed

  • Is Deleted

  • Last Modified Date

  • Owner ID

  • Priority

  • Subject

  • Status

  • Task Subtype

  • Type

  • Who ID

  • What ID


Object: User

Read-only fields

  • Created At Date

  • Email

  • ID

  • Is Active

  • Last Modified Date

  • Name

  • User Role ID


Object: UserRole

Read-only fields

  • ID

  • Last Modified Date

  • Name

  • Parent Role ID

Did this answer your question?