Connect Zapier

When you buy contacts in SmartPropLeads they appear in your CRM, tagged and ready to call — Zapier does the copying. About 10 minutes, no code.

Before you start

• A Pro or Elite plan — integrations are included at no extra charge.
• A Zapier account (the free tier is enough to try it) and a login to your CRM.
• An API key: in SmartPropLeads open Account → Integrations, scroll to API keys, type a name like “Zapier” and press Create key. Copy it now — it is shown only once.

Template or your own mapping — both work

On the Integrations page, a recipe with a Use template button opens a ready-made Zap: every step and field is pre-mapped and you only connect your two accounts. You can change any mapping afterwards, or skip the template and build the Zap yourself with the steps below. Every lead event also carries one CRM note field — score, tier, lead types, why-rationale, mailing address and a link in a single line — so the whole enrichment fits any CRM’s notes or description box without creating custom properties.

The Podio recipe (New skip-traced lead → Podio item)

Every other recipe below is the same five steps with a different app in step 4.

• 1. Start a Zap. In Zapier press Create → Zaps. For the trigger, search for SmartPropLeads and pick it. (While our app is in private beta, open it from the invite link on your Integrations page first.)
• 2. Choose the event. Trigger event: New Skip-Traced Lead. Press Continue.
• 3. Connect your account. Press Sign in, paste the API key, press Yes, continue. Zapier checks the key and shows your plan next to the connection. Press Test trigger — you will see a sample lead (a fixture, marked as such) so you can map fields before your first real purchase.
• 4. Add the action. Press the +, search for Podio, choose Create Item, connect Podio, and pick your workspace and your Leads app.
• 5. Map the fields. Click each Podio field and choose the SmartPropLeads value from the dropdown: Title ← Address; Phone ← Phone primary; Email ← Email primary (the single-value fields — a CRM’s email box rejects the comma-joined Emails list); Owner ← Owner name; Score ← Score; Notes ← Crm note (score, lead types and the one-line reason the lead scored, in one chip). Press Test step — a sample item appears in Podio — then Publish.

That’s it. The next skip trace you buy lands in Podio within a minute of finishing, DNC screening included (Callable phones counts only numbers cleared against the registry).

Other starter recipes

• HubSpot — New Skip-Traced Lead → Create Contact (map Phone primary, Email primary, Address, Owner name; add a second action Create Note with Crm note, or custom contact properties for Score, Tier, Lead types and Why); a second Zap Deal Status Changed → Update Deal matched on Deal id moves your HubSpot pipeline stage.
• REsimpli — New Skip-Traced Lead → Create Seller Lead; add a second Zap Lead Entered Hot → Create Task “call today”.
• GoHighLevel — New Skip-Traced Lead → Add/Update Contact, with the tag SPL-Hot so your pipeline automation takes over.
• Follow Up Boss — New Skip-Traced Lead → Create Contact with source SmartPropLeads.
• No CRM yet — New Skip-Traced Lead → Google Sheets: Create Spreadsheet Row; Lead Entered Hot → SMS by Zapier (or your phone tool).
• Keep your CRM fresh — Score Updated → Update Item in your CRM, matched on Parcel id. Our weekly rescore then keeps your records current forever.

Field mapping cheat-sheet

The same five or six chips do the work in every CRM. Use the single-value Phone primary and Email primary in phone/email boxes (the Phones/Emails lists arrive comma-joined and most CRMs reject them there), putCrm note wherever the CRM keeps free text, set the CRM’s source field to SmartPropLeads, and type TXwhere a state is asked for. Leave everything else blank.

• HubSpot — Create Contact: Email ← Email primary · Phone Number ← Phone primary · Mobile ← Phone secondary · Last Name ← Owner name · Street/City/Postal ← Address/City/Zip · Lifecycle Stage = Lead. Then Create Engagement (Note): Body ← Crm note, Associated Contact ← Contact ID from the previous step.
• Podio — Create Item in a Leads app with fields Title (← Address), Owner, Phone, Email, Mailing address, Score, Tier, Lead types, Notes (← Crm note), Link (← Deal url), Source = SmartPropLeads.
• REsimpli — Create Seller Lead: Last Name ← Owner name · Phone ← Phone primary · Email ← Email primary · Property Address/City/Zip · State = TX · Lead Source = SmartPropLeads · Notes ← Crm note. Second Zap: Lead Entered Hot → Create Task “Call today — {{Address}}”.
• GoHighLevel — Add/Update Contact: Last Name ← Owner name · Email ← Email primary · Phone ← Phone primary · Address 1/City/Postal · State = TX · Source = SmartPropLeads · Tags = SmartPropLeads, SPL-{{Tier}}. Then Add Note ← Crm note. Add a Filter step (Tier is hot) if you only want Hot leads tagged.
• Follow Up Boss — Create Contact: Last Name ← Owner name · Email ← Email primary · Phone ← Phone primary · Street/City/Zip · State = TX · Source = SmartPropLeads · Stage = Lead · Tags ← Lead types. Then Create Note ← Crm note.
• Google Sheets — Create Spreadsheet Row with one column per chip: Address, City, Zip, Owner name, Phone primary, Phone secondary, Email primary, Score, Tier, Lead types, Why, Mailing address, Deal url.

Good to know

• Each Zap you turn on appears on your Integrations page as “managed by a Zap”, with its own delivery log. Turn the Zap off in Zapier and it disappears.
• On a big rescore week you may get a single Rescore summary instead of hundreds of Hot events — that is the cap protecting your Zapier task quota. It carries the counts and a link to the filtered view.
• Events carry only what your plan can see in the app, and only your own data. Contacts pushed to your CRM are for your own permitted use — see our SMS terms before automating texts.
• Prefer Make or n8n? Add a webhook endpoint on the Integrations page instead — the developer docs cover signing and retries.