SharpSpring
Integrations › SharpSpring
CRM

SharpSpring Integration

Create leads in SharpSpring and assign them to active lists automatically -- with custom fields, phone, and lead source pre-populated from your ad forms.

Available Integrations

Connect SharpSpring with 4 lead sources

Start Free Trial No credit card required · 14-day free trial
Trusted by
1,000+ businesses
Leads synced
2M+
Integrations
37+
Free trial
14 days, no card

How It Works

1
Connect Your Ad Account
Link your Facebook, Google, LinkedIn, or TikTok ad account to LeadSync in one click.
2
Choose SharpSpring
Select SharpSpring as your destination and authenticate your account.
3
Map Your Fields
Match your lead form fields to SharpSpring and start syncing leads instantly.

How LeadSync Creates Leads in SharpSpring

SharpSpring (now Constant Contact Lead Gen & CRM) organises contact data around Leads, Opportunities, and lifecycle stages -- a Lead is the unqualified inquiry, an Opportunity is the deal, and lifecycle stage tracks where the contact sits in your funnel. LeadSync connects via your SharpSpring Account ID and Secret Key (semicolon-delimited) and posts each Facebook, Google, LinkedIn, or TikTok lead via the createLeads JSON-RPC method to the SharpSpring API.

Setup is two values from your SharpSpring account (Settings › SharpSpring API). Paste them into LeadSync and the integration enumerates your Active Lists via the getActiveLists RPC method so you can pick which list the lead lands on. Active Lists in SharpSpring are the equivalent of audiences -- they're what your nurture campaigns and email sends key off.

Two-Step Create-Then-Subscribe Pattern

SharpSpring's API doesn't expose a single "create lead and add to list" endpoint -- you have to chain two RPC calls. LeadSync handles this transparently: first createLeads with the lead's firstName, lastName, emailAddress, mobilePhoneNumber, city, and any mapped custom fields, then addListMember with the new lead's ID and the chosen list ID. If the first call fails, the second is skipped and the failure is logged so you can investigate.

The lead's description field is auto-populated with the form name and submission timestamp ("New FB Lead via [Form Name] at [Created At]") so your sales team can see exactly which ad form the lead came from when they open the record in SharpSpring -- no need to manually annotate or rely on an opaque source ID.

Custom Fields and Standard Property Coverage

SharpSpring's standard Lead schema includes firstName, lastName, emailAddress, mobilePhoneNumber, city, plus a description text field for context. LeadSync writes to all of these by default. For the full-name case, the integration calls Utils::parseFullName to split the lead's name into firstName + lastName so SharpSpring email merge tags like {{contact.firstName}} work correctly without manual cleanup.

Beyond the standard fields, SharpSpring custom fields you have defined at the account level appear in the field mapping screen automatically. Map any lead form question to a SharpSpring custom field once, and the value flows into the lead record on every submission -- usable in workflow triggers, email merge tags, and segmentation across your Active Lists.

Frequently Asked Questions

In SharpSpring, go to Settings > SharpSpring API and copy your Account ID and Secret Key. Paste both into LeadSync when adding SharpSpring as a destination. The pair authenticates every JSON-RPC call to the SharpSpring API -- no OAuth flow.
Yes. The connection settings list every Active List in your SharpSpring account (pulled via the getActiveLists RPC method). Pick the destination list and LeadSync chains createLeads + addListMember in a single workflow so the lead is created and subscribed in one operation.
Yes. LeadSync auto-populates the description field with "New FB Lead via [Form Name] at [Created At]" so your sales team can see the exact lead form and submission time at a glance when they open the SharpSpring record. No manual annotation needed.
LeadSync uses Utils::parseFullName to split the lead form's full name into firstName plus lastName when SharpSpring is the destination. This makes SharpSpring email merge tags like {{contact.firstName}} render correctly without a manual cleanup pass.
Custom fields defined at the SharpSpring account level appear alongside the standard fields in the LeadSync mapping screen automatically. Map a lead form question to a SharpSpring custom field once and the value populates on every new lead through that connection.
Yes. SharpSpring workflows triggered by "Lead created" or "Lead added to list" run on records LeadSync creates the same way they run on records created via SharpSpring forms. Build the workflow once and your routing, scoring, or notification logic runs automatically.
Yes. Create one LeadSync connection per source and pick a different Active List on each. Facebook leads can land on a paid-social list while LinkedIn leads land on a B2B list, each with its own segmentation and nurture flow.
Yes. LeadSync supports SharpSpring as a destination for lead forms from Facebook, Instagram, Google Ads lead form extensions, LinkedIn Lead Gen Forms, and TikTok Lead Generation. Each source is its own connection.
The platform was rebranded to Constant Contact Lead Gen & CRM, but the API (Account ID, Secret Key, JSON-RPC methods like createLeads and getActiveLists) is unchanged. Existing customers do not need to re-do their LeadSync setup -- your connection continues to work after the rebrand.

Start Syncing Leads to SharpSpring

Set up your SharpSpring integration in under 60 seconds. Free 14-day trial, no credit card required.

Start Your Free Trial
No credit card required • Set up in 60 seconds • Cancel anytime