Salesforce Guide: Auto-Convert Lead

By default, Chili Piper creates a Lead in Salesforce when there isn’t an Account with an existing Contact matching the same email domain.

Suppose a Lead object is being created by a third-party tool, and you only use Contact and Account in your instance. In that case, we’ve created this guide to “bypass” the Lead object by auto-converting the Lead record and automatically creating a Contact, an Account, and an Opportunity (Optional).

Unmanaged Package Links

The following packages install directly the Lightning Flow and the APEX Class needed in your Instance (Prod or Sandbox) if you need to auto-convert your leads coming from Chili Piper.

Auto-Convert Package (Without Opportunity creation)

• Production Install
• Sandbox Install

Auto-Convert Package (With Opportunity creation)

• Production Install
• Sandbox Install

This post will show you how to automate the lead conversion process using the Lightning Flow by invoking an APEX Class.

Steps

1. Install one package for all users
2. Add the condition: “Meeting Type” IS NOT NULL. => See the Flow Starting Conditions.
3. Adapt the flow to your setup (Optional).
4. Activate the Flow.

The Approach

Our flow is pretty straightforward. Basically, it’ll only run when a new Lead is being created and only if the field “Meeting Type” from Chili Piper is NOT BLANK => Condition to be added to the flow; see the end of the document.

In other words, if a Lead object is being created from Chili Piper, the automation will run to auto-convert

The Auto-Convert process creates automatically:

• A Contact record
• An Account record (If an existing account exists, we’ll create the new Contact under this Account).
• An Opportunity record (depending on the package you decided to install).

All Standard fields (First Name, Last Name, Email, Company..) are already mapped from the Lead object,

If you need to pass custom field values from the Lead Object to the ones above, you’ll need to map your fields:

https://help.salesforce.com/s/articleView?id=sf.customize_mapleads.htm&type=5

Flow Starting Conditions

To make it work only when a Lead is coming from Chili Piper, you’ll need to adjust the flow by adding this entry condition:

“Meeting_Type_CP__C” IS NULL => FALSE

Depending on your setup, you can still add more conditions to this flow.

Is this something you implemented in your org? What is your setup?

Let us know your thoughts and questions, we'd love to know!