Salesforce

How Spara integrates with Salesforce.

Spara support bidirectional data syncs with your Salesforce instance. The Spara platform provides easy-to-use tools to manage field mapping between Spara and your specific Salesforce configuration.

Syncing data from Salesforce to Spara streamlines your buyer's sales process by:

  • Spara never reasks a question

  • Spara's behavior can react to each lead based on where they are in your sales funnel

  • Syncs can be triggered at any point in the conversation

Salesforce Object
Spara reads from Salesforce
Spara writes to Salesforce

Lead

Any field

Any field

Contact

Any field

Any field

Account

Specific fields - see documentation below

n/a

Owner

Specific fields - see documentation below

n/a

Authentication

You must be a Manager-level user to manage third party integrations. You will likely want the individual who manages your Salesforce deployment to complete these instructions.

Navigate to your Integrations page. Click "Authorize" within the Salesforce module. This will lead you through a Salesforce authentication flow. There are no further steps necessary upon completing this flow. You should see that Salesforce is "Enabled" within Spara's Integrations page.

Lead & Contact Objects

Spara can read from and write to any Lead or Contact object. Spara matches its lead to Salesforce Lead/Contact objects by email address or unique SF ID. There are two modes of write behavior:

  • Create New: Spara will create new Salesforce object if no matching record is found

  • Update Existing: Spara will only update an existing, matching Salesforce object

Lead & Contact Field Mapping

Spara's Salesforce Integration page provides easy-to-use tools to map Spara data to Salesforce fields on Lead and/or Contact objects. This lets you customize Spara to your exact Salesforce configuration.

When creating a new field mapping, Spara automatically populates all available Spara data and Salesforce fields. Spara's entire conversation history with a given lead is the "Conversation" Spara field.

Field Mapping in the Spara Platform

Account Objects

Spara reads data from relevant Account objects. This information may be used in configuring Spara's behavior. Account objects are matched according to the following rules:

  1. Converted Lead: If the Lead has been previously converted, we return the associated Account.

  2. Matching Contact: If a Contact exists with the same (case-insensitive) email address as the Lead:

    • We return the Account linked to the most recently created matching Contact.

  3. Matching Company Name: If the user has provided a company name and it matches an Account name, that Account is returned.

If an Account is identified, the following information is stored:

  • salesforce_account_id - The unique identifier of the Salesforce Account

  • salesforce_account_name - The name of the Salesforce Account, which usually represents the company name

  • salesforce_account_owner_email - The email address of the Salesforce Account Owner (i.e. the account's default sales rep)

Owner Objects

Spara reads data from relevant Owner objects, i.e. the assigned sales representative. This information may be used in configuring Spara's behavior. Owner objects are matched according to the following rules:

  1. Spara retrieves the owner of a matching Lead record. If no Lead owner is found...

  2. Spara retrieves the owner of the matching Contact record.

If an owner is identified and is active, the following information is stored:

  • salesforce_assigned_sales_rep_id

  • salesforce_assigned_sales_rep_name

  • salesforce_assigned_sales_rep_email

Additionally, if there is a matching Account object with a default sales rep, the following information is stored:

  • salesforce_account_owner_id - The unique identifier of the Salesforce Account Owner

  • salesforce_account_owner_name - The first & last names of the Salesforce Account Owner

  • salesforce_account_website - The website URL associated with the Salesforce Account

This information may be used in configuring Spara's behavior.

FAQs

How does Spara map to a Salesforce Lead or Contact?

Spara maps to Salesforce objects by either a) Salesforce Object ID, or b) email address. In practice, it's usually easiest to map by email address.

Can Spara upload all message history for a lead into Salesforce?

Spara’s Salesforce integration is configured to upload all messages in a single “thread” to Salesforce. This can be synced to any Salesforce object field, controlled by our Salesforce Field Mapping integration.

Can I create/update both Lead and Contact objects?

Of course! You have independent control over how Spara syncs to Leads objects and Contact objects.

Can you sync the answers to important data that leads share to Salesforce?

Yes! Spara can sync any field or data point that is part of your Journeys. For example, if you have a Journey that asks leads "What is your implementation timeline?" you'll have access to a variable implementation_timeline that you can sync to a Salesforce Lead or Contact object field that you specify. This lets you keep all data in your source-of-truth CRM.

Last updated