Skip to main content

Databook Salesforce Integration: Overview

How the Salesforce integration unlocks new use cases and value for your users

Written by Alex

Overview

Databook's Salesforce integration is a secure, admin-controlled connection between your Salesforce org and Databook. It allows your organisation to share selected CRM data with Databook so that Databook's insights, agents and analytics reflect the accounts, opportunities and teams your go-to-market organisation actually works on.

The value is not the connection itself: it is what becomes possible once Databook can reason over your commercial context. Without CRM data, Databook reasons over external data alone and can only produce outside-in account intelligence. With CRM data, Databook combines your first-party commercial context with its proprietary and third-party data, which is what makes specific, account- or deal-level guidance possible: which accounts to prioritize, what point of view to take into a meeting, where untapped revenue sits, and which deals are at risk.

The integration is designed so that Salesforce administrators retain full control over what is shared. You decide which objects and fields are in scope, and you can change that scope at any time.

What the integration does

The integration enables CRM data to be shared securely with Databook while you retain control over what is shared.

  • Secure authorization. Access is authorized through Salesforce External Client Apps using OAuth. Databook never receives or stores your Salesforce user credentials.

  • Admin-controlled scope. You choose which CRM objects and fields to share, and can include or exclude specific data points at any time so that only the information needed is shared.

  • Read-only data sync by default. The data sync reads the objects and fields you have approved. Databook does not modify or delete your Salesforce records as part of the sync.

  • Simple configuration. Once the package is installed and permissions are set, the sync is configured and started from within Databook.

  • Reliable account mapping. Databook strongly recommends providing a DUNS Number so that Salesforce accounts map accurately to companies in Databook.

By default, the integration syncs a set of standard fields on standard objects such as Account, Opportunity, Contact and User. This default set is a starting point that supports the most common workflows. More complex workflows may require additional custom fields and objects, which we identify together with your team.


Use cases the integration supports

The integration supports two related sets of use cases: the GTM Decision System, which depends on first-party CRM data as a foundational input, and a set of capabilities available in the standalone Databook application today.

The GTM Decision System

The GTM Decision System guides an entire go-to-market organisation, from CRO to BDR, on how to grow revenue efficiently. It does this by helping teams prioritise the most relevant accounts, develop account points of view that generate pipeline and progress opportunities, and identify the risks that could prevent deals from closing.

What makes the GTM Decision System something an enterprise GTM team can actually trust is the combination of a gold-standard data foundation, depth of reasoning, and configurability of the agents, assets and coaches that sit on top of it.

The Databook Context Graph

The GTM Decision System is built on top of the Databook Context Graph, which processes first-party customer data alongside Databook's proprietary and third-party data to identify the events that actually matter at an account or opportunity. It surfaces insights about the key risks, opportunities and developments at an account, at an opportunity, or with a specific buyer that a GTM team needs to understand.

Coupled with Databook's intelligence foundation and reasoning layer, its agentic network of long-horizon, chainable agents customised to your sales methodology and operational plan, and its closed-loop analytics, the Context Graph is the foundation for a guided Decision System that provides trusted advice to GTM teams.

Where the Salesforce integration fits. First-party CRM data is one of the primary inputs to the Context Graph. Without it, the Context Graph can only reason over external signals — it cannot connect a development in the market to the specific opportunity, owner or buying group it affects in your business. The Salesforce integration is how that first-party context reaches the Context Graph.

Use cases: available in the Databook application today

Alongside the Decision System, the integration unlocks three capabilities that enhance the value customers can get from the Databook application.

Streamlined onboarding and account notifications

The integration streamlines onboarding for users across your organisation by automatically following the accounts they own in CRM. Users do not have to search for and manually follow their own book of business before Databook becomes useful to them. Once their accounts are followed, they receive notification insights about key developments at those account, so time-to-value starts from day one rather than after a manual setup step.

Organisation hierarchy sync and closed-loop analytics

Your organisation hierarchy can be synced to Databook from Salesforce. This means the closed-loop analytics Databook provides — showing how your teams are using Databook and what that usage is producing — are aligned to your actual team structure as it is defined in Salesforce. Leaders can see adoption and impact by team without maintaining a parallel hierarchy inside Databook.

CRM-aware agents for complex GTM workflows

CRM data can be used to support agents configured in Databook that combine first-party CRM data with Databook's proprietary and third-party data and insights. This allows complex go-to-market workflows to be optimized end to end: from account planning and prospecting through to building a strategic account point of view that can credibly engage senior sales leaders.

Because agents are configured to your sales methodology and GTM strategy, the specific workflows differ by customer. Examples of workflows this combination enables include:

  • Whitespace recommendations. Databook's reasoning identifies untapped revenue opportunities based on the customer's business priorities and pain, taking into account what has already been sold at the account. This helps teams generate more — and higher-quality — pipeline.

  • Automated account plans. With an understanding of the opportunities and contacts at an account, Databook automates more of the account plan. Unlike traditional account plans, Databook-powered plans stay current as the underlying data changes.

  • Deal acceleration insights and coaching. Databook can surface risks at your opportunities and coach your team on how to unblock stalled deals, based on an understanding of both the customer's priorities, pain and urgency and the deal's history to date. This supports better close rates and more accurate forecasting.


How the integration is set up

Setup is performed by a Salesforce system administrator and is typically a short, guided process. Our team is on hand throughout.

Prerequisite: your Salesforce edition must include API access. Without API access, the integration cannot connect.

  1. Install the managed package. Databook provides a package install URL. The package is installed for all users and should be installed before connecting from within Databook.

  2. Choose the credential the integration will use. This can be either a human user with an appropriate profile, or a dedicated integration user using a Salesforce Integration licence and an API-only profile. An integration user has no UI access, which keeps the integration's footprint tightly scoped.

  3. Configure permissions. Grant API access and read access to the objects and fields in scope, using field-level security or permission sets.

  4. Configure the connected app. Set the OAuth policies for the Databook External Client App so that authorisation persists and the connection is not interrupted.

  5. Connect and configure the sync in Databook. Authorise the connection, select the objects and fields to share, and start the sync.

Some optional capabilities require additional Salesforce permissions beyond the read access needed for the core data sync. These are called out in the installation guide and are only required if you choose to enable those capabilities.

Full step-by-step instructions, including the specific permissions required, are in the public Databook Salesforce Integration Installation Guide.


Trust, security and how Databook uses customer data

Databook uses customer data, including CRM data, only for the purposes set out in our Master Subscription Agreement with you.

To ensure customer data is used only for those agreed purposes, we have designed and implemented organisational, contractual and technical controls. Databook is SOC 2 Type 2 certified. Further detail on our controls is available in our Trust Center and our security and privacy FAQs.

The Salesforce integration itself is designed with the security and privacy of customer CRM data in mind. Its key design principles are:

Principle

What it means

Tenant isolation

Each customer tenant runs with dedicated compute resources.

Identity segregation

Tenant-specific service principals operate with least-privilege access.

Data lineage

Movement of records is tracked from source to destination.

Security-first design

A zero-trust architecture requires permissions to be granted explicitly.

Secure authentication

Access is managed through Salesforce External Client Apps, without sharing credentials.

Customer control

Salesforce administrators decide which objects and fields are in scope and can change that scope at any time.

The integration runs on Databook's existing multi-tenant architecture, with strong data isolation and row-level security.

Find out more about security and privacy in Databook's Trust Center.

Did this answer your question?