Skip to content
Integration · CRM

Your CRM has the facts. Your collateral should know them.

Bidirectional sync between Salesforce and Assay's Truth Graph means every artifact is personalized to the live opp - no merge fields, no copy-paste, no stale snapshots.

Audit Your Library → See a Demo
Direction
Salesforce ⇄ Assay
Sync
Real-time webhooks (< 5s latency); hourly fallback poll for missed events
Auth
OAuth 2.0
Data flow

Assay subscribes to Salesforce webhooks for Opportunity, Account, Contact, and Custom Object changes. When an opp progresses through configurable stages, Assay generates personalized proposal artifacts using Account and Opp custom fields as Truth Graph variables. The audit trail and engagement signals from generated artifacts flow back into Salesforce as custom fields on the Opportunity.

What you do with it

Auto-personalize proposals from opp data

When an opp moves to stage 3 (Proposal), Assay generates a proposal pre-populated with account-specific compliance, integration, and pricing details from the live Salesforce record. No merge fields, no copy-paste.

Surface battlecards on the Salesforce opp page

Embed the right Assay battlecard directly in the Lightning UI based on the Opportunity's competitor field. Reps never leave Salesforce to find the right battlecard for the deal they're working.

Trigger RFP response composition from a Custom Object

Define a 'Security Questionnaire' Custom Object on the Opportunity. When a record is created with an attached PDF, Assay parses the questionnaire and composes a draft response within 90 seconds - visible inline on the opp.

Audit which deals used stale claims

Cross-reference Assay's audit trail with closed-won/closed-lost data in Salesforce to identify deals where stale collateral correlated with deal outcome. Surfaces drift before it costs you the next renewal.

Personalize ROI calculators per opp

Map Salesforce custom fields (rep count, revenue, current spend) to Truth Graph variables. The ROI calculator embedded in your proposal renders with the prospect's actual numbers, not generic placeholders.

Setup in 6 steps

  1. 01
    From your Assay admin panel, click Integrations → Salesforce → Connect
  2. 02
    OAuth into Salesforce as a System Administrator (read access to Opportunity, Account, Contact, and any Custom Objects you want to use)
  3. 03
    Map your Salesforce standard and custom fields to Assay Truth Graph variables - Assay auto-suggests mappings; review and confirm
  4. 04
    Configure trigger stages (e.g., 'On stage change to Proposal, generate proposal artifact')
  5. 05
    Test the integration by promoting a test opp through the configured stages - verify the generated artifact populates correctly
  6. 06
    Enable the Lightning Component for in-CRM access (optional, requires admin to add the component to the Opportunity Lightning page)
Permissions required
  • Read access to Opportunity, Account, Contact, and User standard objects
  • Read access to any Custom Objects you want to use as Truth Graph variables
  • Read access to custom fields specified during the field-mapping step of setup
  • Optional: Write access to a custom 'Assay Audit Trail' field on Opportunity (for the closed-won/closed-lost audit use case)
  • Optional: API access for the Lightning Component to fetch artifacts in-line
FAQ

Frequently Asked Questions

Does this integration require admin access on Salesforce?
Initial setup requires a System Administrator for OAuth and field mapping. Day-to-day operation does not require admin access - reps interact with Assay through the Lightning Component or directly via Assay's UI, both of which respect Salesforce's existing record-level permissions.
What data does Assay store from Salesforce?
Assay stores only the field values you explicitly map to Truth Graph variables, plus the IDs needed to maintain bidirectional sync. Raw Salesforce records are never persisted - they're fetched at composition time and discarded. Generated artifacts and their provenance metadata are persisted in Assay.
How is this different from Salesforce's native AI features (Einstein)?
Einstein is sales-rep-facing AI for forecasting, lead scoring, and call summarization. Assay is artifact-generation infrastructure - it produces the documents reps send to prospects. The two are complementary; Einstein doesn't generate proposals, Assay doesn't score leads.
Does this work with Salesforce Sales Cloud, Service Cloud, or both?
Both. Sales Cloud is the primary integration surface (Opportunity, Account, Contact). Service Cloud is supported for support-collateral use cases (Cases, Knowledge articles as Truth Graph sources).
What happens if the Salesforce field schema changes?
Assay's mapping layer detects schema changes within an hour and surfaces them in the admin panel as 'mapping needs review'. Existing mappings keep working until you actively change them; new fields can be mapped at your team's pace.

Continue exploring

Use Case

Automate RFP Responses: How RevOps Teams Cut Response Time 90%

Stop drowning in 100-question RFPs. See how Series B–C RevOps teams use Assay's Truth Graph to deliver verified, sourced responses in under 90 seconds.

→
Comparison

Assay vs Seismic: 2026 Buyer's Guide for Series B–C SaaS

Honest 2026 comparison of Assay vs Seismic - pricing, features, migration realities. See why Series B–C teams skip Seismic and pick Assay.

→
Commercial Truth Infrastructure

Connect your source of truth. Stop copy-pasting forever.

Wire Salesforce into Assay in under 10 minutes. Every artifact you ship will reflect what's actually true today.

Audit Your Library → Book a Demo