Salesforce
A guide on how to integrate Default with Salesforce.
Integration
Navigate to the Integrations tab within Default. Then Select Salesforce to connect, manage, or disconnect your CRM integration.
A Salesforce admin that connects Default with your CRM will be listed as a user creating all records. A good practice is to have a dedicated “Integration User” with admin permissions to authenticate Salesforce to take away any confusion from the “Created By” field being the human Default admin.
Nodes
Node Field Mapping
In Salesforce nodes, you can pass data such as form submission answers, enrichment data, or custom values for any Salesforce field.
Dropdown on the right shows Default data.
Dropdown on the left maps your Salesforce instance's fields.
Default allows you to create, match, and update records. Below is an overview of each action:
Create
Salesforce Create Nodes allow you to create any Salesforce object and pass form submission answers, enrichment data, or custom values for any field (including custom fields).
Match
Salesforce Match Nodes allow you to find any Salesforce object. Match nodes can create 2 paths for objects that match or don't match your set criteria.
You can stack as many criteria as you want. And if you have duplicate records you can prioritize records. The example below shows if multiple Accounts come back with the same name, Default can pick the one that has the most recent activity (hence Last Modified Date = Max).
Merge
Salesforce Create Nodes allow you to update (merge) any Salesforce object with new data such as form submission answers, enrichment data, or custom values for any field (including custom fields).
Objects
Default supports Salesforce objects listed below:
Leads
Default allows you to create, merge, and match Leads. You don't have to use any other tool to send lead information for subsequent posting to Salesforce. Here's how it works:
Leads are submitted via the imported form from your website into Default.
Default utilizes various criteria, including form question responses and our enrichment data, to match existing Leads, Contacts, or Accounts (including fuzzy matching).
If a match is found, Default can update the fields you specify in Salesforce.
If there is no match, Default creates a new record in Salesforce using the data provided from the form submission enrichment data, or a combination of both.
Contacts
Default allows you to create, merge, and match Contacts. If Lead-to-Contact conversion is happening during your workflow, it's best to use the Salesforce Match node and look for a Contact with Lead's attributes.
Accounts
Default allows you to create, merge, and match Accounts. If Lead-to-Account conversion is happening during your workflow, it's best to use the Salesforce Match node and look for an Account with Lead's attributes.
Routing
Assigning User to Object
Default can assign any Salesforce object using the Round-Robin node. Here is how it works:
Select a Round-Robin node and configure based on which Queue Default should route
Select a Create node to create a new record
Map "Owner from the step Round-Robin" over to the Salesforce Owner ID field
If you want to update the existing record's Owner, first you need to Select a Match node and then select a Merge node and update the Owner ID field following the same instruction from above.
Important! Make sure you have completed the User Mapping! This is a critical step.
Ownership-based routing
Default can reference the name of the Lead/Contact or Account Owner in Salesforce and show the calendar of the object owner.
To enable ownership routing by account owner, follow these instructions:
Configure the Match node to find a record in question.
Select a member called: "Owner from the previous step" while configuring the Display Scheduler node.
Duplicates
Default verifies duplicates and can refrain from generating a lead if the email is already registered in the Salesforce system.
Default will first check for a matching lead in the Salesforce system (Using a Match node)
If a match is not found, Default will proceed to create a new lead.
If a match is found, Default will tag them as duplicates.
Regardless of whether a new lead was created or a match was found, an event object is associated with the lead.
Rest assured that Default is designed to efficiently handle duplicates and lead creation in these scenarios.
If your flow requires sending all leads to Salesforce without conducting duplicate checks, Default can create a Lead every time.
Prioritizing Mapping with Duplicate Accounts
To handle prioritization in cases of duplicate accounts, you can utilize the prioritization logic available under the Match node. This functionality allows you to establish priorities based on other fields associated with the Company.
Events
Configure the behavior of event tracking in Salesforce based on meetings booked in Default. You can relate Salesforce Events to a Lead or Contact.
Some teams operate on Leads, some go straight to Contacts. This setting allows to service both ways. Click here to edit event logging settings.
Event Field Mapping
In Salesforce integration settings you can set custom values for Event object created within Default. Most customers select custom value = Inbound and map that over to Salesforce's Source field to ensure comprehensive tracking.
Last updated