LionDesk and RealScout run as separate systems. Zapier creates RealScout contacts from your LionDesk leads and can log RealScout property activity back into LionDesk — but some LionDesk features do not have RealScout equivalents and do not sync.
Before you build: what Zapier does and does not do
What works through Zapier | What does NOT work through Zapier |
New LionDesk contacts → RealScout Contacts | Tags from LionDesk do not flow to RealScout |
Lead Source values from LionDesk Source field | LionDesk drip campaigns do not sync to RealScout Auto Nurture |
RealScout property activity → LionDesk notes, tasks, or tags | Not all LionDesk Custom Fields are available in Zapier |
Email, name, phone, and select optional fields | Transaction tracking and video texts do not sync |
LionDesk's Zapier app is functional but lean. It delivers reliable contact creation and basic activity routing, not a full feature bridge. Set expectations accordingly before you build.
Step 1: Connect LionDesk and RealScout in Zapier
Log in to Zapier and click + Create Zap.
In the Trigger step, search for LionDesk and select it.
Authorize LionDesk using your LionDesk credentials when prompted.
In the Action step, search for RealScout and select it.
Authorize RealScout using your RealScout credentials when prompted.
Confirm both apps show as Connected in your Zapier account.
Step 2: Choose your LionDesk trigger
Trigger | When to use it |
Tag Added to Contact | Recommended. Only contacts you tag with a specific value flow to RealScout. You control enrollment. |
New Contact | Fires for every new LionDesk contact. Use only if you want all new leads to sync automatically. |
Tag-gated enrollment is the default recommendation. If your LionDesk database includes contacts with no engagement in 12 or more months, syncing them all creates email deliverability risk. Tag-based enrollment lets you add contacts in manageable batches.
To set up tag-gated enrollment:
Create a dedicated tag in LionDesk such as "RealScout-Enrolled."
Set the Zapier trigger to Tag Added to Contact and specify that tag.
When you want a contact to flow to RealScout, apply the tag in LionDesk. The Zap fires automatically.
Step 3: Map fields from LionDesk to RealScout
Set the Action to RealScout → Create Client and map fields:
RealScout Field | Map From LionDesk | Required? |
LionDesk email field | Yes | |
First Name | LionDesk first name field | Yes |
Last Name | LionDesk last name field | Recommended |
Primary Mobile Phone | LionDesk phone field | Optional |
Lead Source | LionDesk Source field | Strongly recommended |
Lead Source mapping: If your LionDesk Source field is often empty, add a fallback static value in the Zap such as "LionDesk Manual." This ensures every RealScout contact has a Lead Source, which enables Lead-Source-keyed Templates. Not all LionDesk Custom Fields surface in Zapier — test field mapping with a real contact before publishing.
Step 4: Test and publish
In LionDesk, apply your enrollment tag to a test contact.
In Zapier, click Test trigger and confirm the LionDesk contact data appears.
Click Test action and confirm the contact is created in RealScout.
Open Contacts in RealScout and verify the test contact appears with the correct Lead Source.
Click Publish Zap.
Step 5: Set up Auto Nurture in RealScout
Because tags do not flow through Zapier, Auto Nurture is your primary coverage mechanism for Zapier-enrolled contacts. Choose one nurture engine per contact — either LionDesk drip campaigns or RealScout Auto Nurture, not both. Running both creates duplicate email touches and inflates unsubscribe risk.
Open Auto Nurture and click Update Settings.
Set Default Map Location to your primary market.
Set automation mode to All new contacts.
Under Fallback Templates, select a Listing Alert Template and a Market Activity Alert Template.
Build Templates in RealScout keyed to your LionDesk Lead Source values where segmentation makes sense.
Step 6 (Optional): Route RealScout activity back to LionDesk
LionDesk's Zapier app supports adding tags, notes, and tasks as actions. Build a second Zap to log RealScout property activity in LionDesk:
Create a new Zap with trigger RealScout → Property Saved (Interested).
Set the action to LionDesk → Add Note with property details, or LionDesk → Add Tag (for example, "RS-Interested"), or LionDesk → Create Task with a follow-up date.
Publish the Zap.
Note: adding a tag in LionDesk via this Zap is a LionDesk-side action. It does not cause tags to flow into RealScout — that platform constraint remains in place.
Maintaining your Zap over time
Check Zap history weekly for the first month, monthly thereafter.
Watch for LionDesk field changes. Renaming a Custom Field that was mapped in the Zap causes it to fail silently. Re-map and re-test after any field restructuring.
Stagger your initial backfill. Tag contacts in batches of 25 to 50 at a time over multiple days to protect email deliverability in your first 14 days on RealScout.
Related Articles