​

​

Overview

When connecting Default with Salesforce as an admin, you will be listed as the user creating all records. To avoid confusion with the Created By field displaying the Default admin’s name, it’s recommended to use a dedicated Integration User with admin permissions to authenticate Salesforce.

This approach offers two key benefits:

• Ensures that all records created via Default are consistently attributed to the Integration User and not a human admin.

• Reduces the risk of integration breakage if the designated user leaves the company or has their account permissions altered in Salesforce.

​

Salesforce Integration

​

Step 1: Navigate to Integrations

​

Salesforce Nodes

​

Create, Match, and Update Records

​

Create Records

The Salesforce Create node enables you to create any Salesforce object type while passing form submissions, enrichment data, or custom values to any field, including custom Salesforce fields.

​

Match Records

The Salesforce Match node allows you to search for any Salesforce object type and create two distinct paths based on whether the objects meet your specified criteria. You can define as much or as little criteria as needed.

If duplicate records exist, you can prioritize which record to select:

• Choose the record with the most recent activity (e.g., Last Modified Date = Max).

• Apply additional logic to identify the best match based on your requirements.

Refer to the de-duplication section of this guide for more information on record duplication and how to override Salesforce default settings!

​

Update Records

The Salesforce Update node allows you to update any Salesforce object type with new data such as form submission answers, enrichment data, or custom values for any field (including custom fields).

​

Common Use-Cases

​

Managing Leads, Contacts, and Accounts in Salesforce

Default simplifies lead management by handling the entire process—from form submission to Salesforce updates—without needing additional tools.

Use Default to create, match, and update your Salesforce Leads, Contacts, and Accounts with easy-to-set parameters via workflows.

​

Create or Match an Opportunity

Default can also take ownership of your Opportunity management in Salesforce.

Here’s how it works:

• A Lead submits a form on your book a demo page.

• Default workflow is used to Create/Match to Lead/Contact/Account.

• Look for an existing Opportunity, if none found then create a new one.

• (Optional) Create an OpportunityContactRole on the Opportunity.

​

Lead Conversion in Default

Default provides flexibility to convert leads into contacts, create new accounts, or connect them to existing accounts. You can also convert leads into existing contacts and link them to existing opportunities.

Here’s how it works:

1. Lead Submission Leads are submitted via your website’s imported forms into Default.

2. Matching Criteria Default uses multiple criteria, including form responses and enrichment data, to match leads with existing Leads, Contacts, or Accounts. Fuzzy matching is also supported for partial matches.

3. Field Updates in Salesforce If a match is found, Default can update specified fields in Salesforce automatically.

4. Converting Leads Add the Convert Salesforce Lead Node to your workflow to process the lead conversion:

   • Specify whether to create a new account or merge with an existing account.

   • Optionally, create an opportunity linked to an existing contact during lead conversion.

5. Customizing Opportunities If creating opportunities isn’t part of your workflow, simply toggle off the opportunity creation option within the node settings.

​

Routing

Default provides the option to do queue-based routing of records or ownership-based routing.

​

Queue-based Routing

Here’s how it works:

• Select a Round-Robin node and configure based on which Queue Default should route.

• Select a Create Salesforce Record node to create a new record.

• Select the record type.

• Map Owner from Round-Robin over to the Salesforce Owner ID field.

​

Owner-based Routing

Default uses the email address of a lead or contact to run through the configured logic, matching it to ownership fields—typically the owner_id in Salesforce.

Once a match is identified, Default deterministically displays the calendar for the corresponding record owner, ensuring accurate routing, within seconds.

Here’s how it works:

• Configure the Match node to locate the record in question (eg. Lead/Contact/Account).

• Add a Display Scheduler node.

• Select the following: Display Scheduler > Queue/Member > Owner from previous record.

​

Duplication Logic

​

Overview

Default is designed to efficiently manage duplicates while creating leads in Salesforce.

Here’s how it works:

• Duplicate Verification Default checks for duplicates by verifying if the email address is already registered in Salesforce. If a duplicate is found, Default can refrain from generating a new lead.

• Match and Prioritization

  • Default first searches for a matching lead in Salesforce using a Match Node.

  • If no match is found, Default creates a new lead.

  • If a match is found, Default can prioritize it using the configured logic within the Match Records node.

• Event Association Regardless of whether a new lead is created or a match is found, Default associates a scheduled event or event object with the lead.

• Bypassing Duplicate Checks If your workflow requires sending all leads to Salesforce without checking for duplicates, Default can be configured to create a new lead for every submission.

This flexible approach ensures your lead management process aligns with your specific business needs.

​

Creating Duplicates

Based on customer feedback and learnings, we’ve identified scenarios where creating duplicate records is necessary. This often stems from Salesforce’s default de-duplication logic not aligning with your business requirements.

To address this, we’ve introduced an optional toggle on the Create Salesforce Record node (see below).

​

How It Works

• When the toggle is enabled, you can specify a field (e.g., email) to check for duplicates.

• If no match is found for the specified field, Default will create a new record.

​

Example Use Case

• Existing Record: joe.smith@apple.com is already a Lead in Salesforce.

• New Submission: joe.smith2@apple.com submits a form.

• Salesforce’s default Logic: Considers this the same Lead due to overlapping criteria.

• Default’s Match Field Logic: With the match field set to email, Default identifies that the emails do not match and creates a new Lead record instead.

​

Prioritizing Duplicates

To handle prioritization in cases of duplicate accounts, you can utilize the prioritization logic available under the Salesforce Match node. This functionality allows you to establish priorities based on other fields associated with the Account/Company.