LionDesk
Integrations › LionDesk
CRM

LionDesk Integration

Route real estate leads to LionDesk CRM automatically -- with source tracking, contact assignment, and custom field mapping built for agents and brokerages.

Available Integrations

Connect LionDesk 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 LionDesk
Select LionDesk as your destination and authenticate your account.
3
Map Your Fields
Match your lead form fields to LionDesk and start syncing leads instantly.

How LeadSync Creates LionDesk Contacts

LionDesk's v2 API (api-v2.liondesk.com) uses a Bearer token for authentication -- a single long-lived Access Token you generate in your LionDesk account under Profile › Integrations. LeadSync stores the token, then POSTs to /contacts with the lead's name, phone, email, and any mapped real estate fields whenever a Facebook, Google, LinkedIn, or TikTok lead arrives.

Before each contact create, LeadSync calls GET /contact-sources and looks up the LionDesk contact source named "Facebook" -- pulling its id and user_id. Those values become source_id and assigned_user_id on the new contact, so every paid-social lead lands attributed to the correct source and routed to the correct agent without you having to set assignment rules manually.

Real Estate Fields and Custom Field Support

Real estate teams often need more than first/last/email/mobile. LeadSync's LionDesk mapping screen exposes the full list of LionDesk SYSTEM properties -- home_phone, office_phone, fax, company, birthday, anniversary, spouse_name, spouse_email, spouse_phone -- so you can map a lead form question like "Spouse / Partner Name" straight onto the correct LionDesk slot rather than dumping it into a notes field.

Beyond system properties, LeadSync calls GET /custom-fields and lists every custom field defined on your LionDesk account (prefixed with CUSTOM: internally). Map a lead form question once, and LeadSync wraps the value in LionDesk's required {id, value} shape inside the custom_fields array on the contact create payload.

Full-Name Splitting for LionDesk

Facebook lead ads default to a single full_name field rather than separate first/last fields. LionDesk wants them split -- first_name and last_name are separate properties, and email merge tags like {{first_name}} only render correctly when first_name is populated alone.

LeadSync detects when only full_name is present and runs Utils::parseFullName to split it. "Jane Maria Smith" arrives in LionDesk as first_name "Jane" + last_name "Maria Smith" so personalised email and SMS drip campaigns render correctly without an agent having to fix every record by hand.

Frequently Asked Questions

In LionDesk, click your initials top-right and choose Profile, then Integrations. Generate or copy your API Access Token (a 40-character hex string). Paste it into LeadSync when you create the LionDesk connection -- LeadSync stores it encrypted and uses it as the Bearer token on every api-v2.liondesk.com request.
LeadSync queries LionDesk's contact-sources endpoint, finds the source named "Facebook" (LionDesk creates this by default), and uses its id as source_id on the new contact. The "Facebook" source's assigned user also becomes the contact's assigned_user_id, so every paid-social lead is routed to the correct agent automatically.
Yes. LionDesk has dedicated spouse_name, spouse_email, and spouse_phone properties, and LeadSync's mapping screen exposes all three. Add the questions to your Facebook lead form, then map them onto the correct LionDesk slot. The data is searchable and surfaces in the LionDesk contact view alongside the primary contact details.
Yes. LionDesk drip campaigns triggered by "New Contact Added" or by source assignment fire on contacts LeadSync creates the same way they fire on contacts created manually or via LionDesk web forms. Build the drip once and every new paid-social lead enters automatically.
All three are supported -- mobile_phone, home_phone, and office_phone are separate LionDesk SYSTEM properties and all three appear in the LeadSync mapping screen. If your lead form captures multiple phone numbers, you can route each to its own LionDesk slot.
When the lead arrives with a single full_name field (the Facebook default), LeadSync runs Utils::parseFullName to split it. Common multi-word names like "Mary Jane Smith" are handled correctly so first_name is "Mary" and last_name is "Jane Smith". This makes LionDesk merge tags like {{first_name}} render correctly in your drips.
Yes. Each LeadSync connection picks its own LionDesk source automatically based on the source name. Facebook leads land tagged "Facebook"; LinkedIn leads can land tagged "LinkedIn" if you create that contact source in LionDesk first. This gives you accurate per-channel attribution in your LionDesk reports.
Yes. LeadSync supports LionDesk as a destination for Facebook Lead Ads, Instagram Lead Ads, Google Ads lead form extensions, LinkedIn Lead Gen Forms, and TikTok Lead Generation. Each source is its own LeadSync connection but they all use the same LionDesk integration helper.
LionDesk allows multiple contacts with the same email by default. If you want to de-duplicate, enable LionDesk's built-in duplicate detection (Settings > Duplicate Manager) and it will merge contacts by email or phone within the LionDesk app rather than at the LeadSync layer.

Start Syncing Leads to LionDesk

Set up your LionDesk 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