Upcoming Feature
Salesforce Integration
The Salesforce integration lets in-house legal teams query CRM records directly from Harvey Assistant — bringing account, contact, opportunity, and case context into legal workflows without manually searching across systems.
What's Coming
Customer and deal context lives in Salesforce while legal work happens in Harvey — and closing that gap has meant manual record hunting and constant context switching. The Salesforce integration removes that friction entirely. Users can query accounts, contacts, opportunities, leads, and cases in natural language directly from Harvey Assistant, and use the results immediately as context for follow-on legal work — all without leaving Harvey.
Feature Highlights
- Query Salesforce accounts, contacts, opportunities, leads, and cases using natural language from Harvey Assistant
- Bring CRM context directly into legal workflows — no manual exporting or copying between systems
- Identify contract-related records stored in supported Salesforce standard objects
- Query multiple object types in a single workflow when relevant relationships are accessible
- Permissioned access governed by Salesforce integration's user and workspace configuration
- Use Salesforce context to answer targeted business and legal questions before reviewing or negotiating an agreement
FAQs
Q: Can Harvey query Salesforce today?
The initial Salesforce integration is designed to let users query supported standard Salesforce objects through Harvey Assistant. Current internal scope includes Account, Contact, Opportunity, Lead, and Case records. Confirm current availability and the customer's required object/field coverage before committing.
Q: Can Harvey pull our Salesforce contracts into Vault?
Contract sync into Vault is a later-phase use case in the internal roadmap. The initial integration is focused on standard CRM context and does not automatically provide repository-wide contract sync. First confirm where the contracts live, which Salesforce objects hold them, and whether the customer needs file selection or full synchronization.
Q: Our contracts are in Salesforce Files. Are they supported?
Do not assume that Salesforce Files or attachments are included in the initial scope. Confirm the release and the customer's specific file model. File-picker, attachment, and custom-object access are separate scope areas identified for later phases.
Q: Our agreements are in a custom object. Will this work?
The initial v1 scope is centered on standard Salesforce objects. Capture the custom object, fields, relationships, and document location so Product and Solutions can determine whether the use case fits the current release or requires later-phase support.
Q: What does the Salesforce user see?
The connected experience is surfaced through Harvey Assistant. The information Harvey can access is governed by the Salesforce integration credential, workspace configuration, and the permissions available to that integration user.