Articles on: CRM Integrations

How to connect SmartMoving to LeadTruffle (Pro API vs. Leads API)

📝 Choose between the SmartMoving Pro and Leads APIs, connect one, and control when and where LeadTruffle sends your leads.



Table of contents




Overview


An API is simply a way for two apps to share information. LeadTruffle offers two separate ways to send a lead into SmartMoving, and you'll see both on the integrations screen:



  • Smart Moving Pro API — the more advanced, paid option. Requires a specific SmartMoving plan plus paid Open API access.
  • SmartMoving Leads API — the simple, free option. SmartMoving makes it available on every plan.


Both connections are one-way: LeadTruffle pushes lead info to SmartMoving. Neither one pulls changes back from SmartMoving, books a move, or updates an existing SmartMoving job.


Turn on only one of these connections. If both are active, the same lead can be sent to SmartMoving twice.



Pro API vs. Leads API at a glance



Smart Moving Pro API

SmartMoving Leads API

Who can use it

SmartMoving Growth Plan customers with Premium Open API access

Customers on any SmartMoving plan

SmartMoving cost

SmartMoving currently lists Premium API access around $149/month

Free — no API subscription needed

Key needed

Open API Key

Provider Key

What it sends

A customer record and a lead record

One lead record

Checks for a match

Yes — tries to match customers and recent leads by phone number

No duplicate check

Branch routing by Google LSA account

Yes

No

Best for

Customers who already pay for Premium API access

Most customers who just need new leads sent over


SmartMoving offers two Open API levels. Basic is read-only. Premium lets an outside app create records. Because LeadTruffle creates records, Basic access is not enough for the Pro connection.


SmartMoving sets its own plan names and pricing, and they can change. Confirm current details in the SmartMoving Open API guide before relying on a price or plan.



Which connection should you use?


An easy way to think about it:


  • The Leads API is like a mail slot. LeadTruffle drops a new lead into SmartMoving, but can't look around inside first. Free, simple, and enough for most people.
  • The Pro API is like a larger door. LeadTruffle can look for a matching customer or recent lead, then create records as needed. SmartMoving charges for this wider access.


If you only need new leads to land in SmartMoving, choose the Leads API. Choose the Pro API if you already pay for Premium Open API access and want customer matching, or if you need to send leads from different Google LSA accounts to different SmartMoving branches.



What information gets sent to SmartMoving


Once LeadTruffle has gathered the details, it can send:


  • Name, phone number, and email
  • The starting address, when known
  • The lead source and helpful notes
  • A link to the full LeadTruffle conversation
  • Missed-call and voicemail details, when they exist
  • Answers gathered by LeadTruffle
  • Website tracking details, such as the campaign name, when known


The Pro API also labels the referral source as LeadTruffle.


Some lead sources hide the customer's real phone number or email. See Leads with masked phone numbers or emails to control whether those are sent.



When leads are sent to SmartMoving


LeadTruffle gives the AI time to collect details before sending a lead to SmartMoving. You control this wait in Settings → AI Data Sync under Send after. The default is 20 minutes.


  • The wait is measured from when the lead arrives, even if the lead never replies.
  • When the wait ends, LeadTruffle sends the details collected so far, once there's been at least one minute with no new messages.
  • If the AI collects everything your prompt asks for sooner, the lead is sent right away.
  • Phone call leads are sent when the call ends.


The same timing applies to team notifications and the Conversation complete webhook. Changes apply to new leads and to leads still waiting to be sent. Allow about an extra minute for processing.


Don't see a new lead in SmartMoving yet? It may still be inside the Send after wait window.



Leads with masked phone numbers or emails


Some lead sources, like Google LSA, hide the customer's real contact details behind temporary phone numbers or relay emails.


The Don't sync masked data from third-party lead sources setting is unchecked by default. While it's unchecked, leads that only have masked contact details still sync to SmartMoving.


When you check it:


  • LeadTruffle leaves temporary third-party phone numbers and email addresses out of the sync.
  • If SmartMoving requires real contact details and the lead doesn't have them, LeadTruffle waits instead of sending the lead.


You'll find this setting on the Connection tab. See How to edit an existing connection.



How to connect the Pro API


Before you start, confirm both of these in SmartMoving:


  1. You're on the SmartMoving Growth Plan.
  2. Your Open API level is Premium — not Basic.


Then:


  1. In SmartMoving, go to Settings → Integrations → SmartMoving API.
  2. Turn on the Open API and copy your Open API Key.
  3. In LeadTruffle, click Connect on the Smart Moving Pro API card.
  4. Paste your API Key and save.


Not sure which level you have? A Basic (read-only) key looks fine at first but fails when LeadTruffle tries to create a record. See Testing your connection below.



How to connect the Leads API


  1. In SmartMoving, go to Settings → Sales → Lead Providers → Your Website → View Instructions.
  2. Copy your Provider Key.
  3. In LeadTruffle, click Connect on the SmartMoving Leads API card.
  4. Paste your Provider Key and save.


The SmartMoving Lead API guide confirms this API is free and available on all SmartMoving plans.


The two keys are not interchangeable. A Provider Key won't work in the Pro API box, and an Open API Key won't work in the Leads API box.



How to edit an existing connection


Once SmartMoving is connected, click Settings on the connected card to make changes. The card also shows when the connection was last checked, plus the Test Connection, Test Sync, and Disable buttons.


On the Smart Moving Pro API card, the Configure Smart Moving Integration window has two tabs:


  • Connection — your API key, the Don't sync masked data from third-party lead sources setting, and the Enable integration checkbox. Click Save connection to save changes on this tab.
  • Branch routing — choose which SmartMoving branch receives leads from each connected Google LSA account. Click Save changes to save changes on this tab.




Each tab saves separately. If you change both tabs, save both.


The Branch routing tab is only available on the Pro API. The Leads API doesn't support branch routing.



Route Google LSA leads to different SmartMoving branches


If you run more than one SmartMoving branch, you can send leads from each Google LSA account to a specific branch.


Branch routing requires the Smart Moving Pro API connection. It isn't available on the Leads API.


Add a mapping


  1. Go to External Integrations and click Settings on your Smart Moving Pro API card.
  2. Open the Branch routing tab.
  3. Click + Add mapping.




  1. Choose the Google LSA account the leads come from.
  2. Choose the SmartMoving branch that should receive them, then confirm the mapping.



  3. Repeat for each Google LSA account, then click Save changes.


Your mappings appear in a table showing the Lead source, Account (name and account ID), CRM, and Branch for each one. To change or delete a mapping, click Edit or Remove on that row, then click Save changes.



Save changes stays greyed out until you make a change.


Mapping rules


  • Each Google LSA account can have one mapping.
  • Several Google LSA accounts can send leads to the same branch.
  • Renaming a Google LSA account or SmartMoving branch won't break your mappings.
  • Each inquiry uses its original Google LSA account to choose a branch, not the contact's most recent source.


When no Google LSA mapping matches


This setting decides where leads go when their Google LSA account isn't mapped. It's also used if a mapped branch becomes unavailable. Choose one:


  • Keep current SmartMoving routing (default) — sends leads wherever SmartMoving normally places them.
  • Send to a selected fallback branch — sends unmapped leads to the branch you pick.


If a mapped branch becomes unavailable


If a branch you've mapped is no longer available in SmartMoving:


  • Leads from that account follow your When no Google LSA mapping matches setting instead.
  • The mapping is kept and marked Needs attention so you can fix it.
  • Click Edit on the flagged mapping, choose an available branch, and click Save changes.


Unavailable branches can't be selected for new mappings or as your fallback.


Saving and canceling


Changes on the Branch routing tab aren't applied until you click Save changes. Clicking Cancel discards your changes. If you close the window with unsaved edits, LeadTruffle asks before discarding them.


Branch routing applies to future submissions only. Existing records stay in their current branch.



Testing your connection


How testing behaves depends on which connection you're using.


Pro API


  • Test Connection only reads one recent SmartMoving customer — it does not send a LeadTruffle lead.
  • Test Sync sends your most recent LeadTruffle lead to SmartMoving.
  • A Basic (read-only) key may pass Test Connection but fail Test Sync, because the first only reads data while the sync must create it. If this happens, confirm you have Premium API access.


Leads API


  • Save, Test Connection, and Test Sync can each send your latest LeadTruffle lead to SmartMoving.
  • You need a recent LeadTruffle lead to test. With no recent lead, the setup saves but can't be marked connected yet.


Testing may create a real lead in SmartMoving — not a sample. Let your team know before you run a test so no one is surprised by a test record.



Using other tools that send leads to SmartMoving


If another tool (for example, a Zapier automation) also sends the same leads to SmartMoving, you can end up with a separate record from each tool.


  • Leads API: there's no duplicate check, so each tool creates its own record.
  • Pro API: phone-number matching may catch some of these, but don't rely on it to clean up duplicates from other tools.


To avoid duplicates, send each lead source to SmartMoving through only one tool.



Troubleshooting


If a lead didn't reach SmartMoving, check these in order:


  1. The wait time hasn't ended yet. By default, leads are sent 20 minutes after they arrive. See When leads are sent to SmartMoving.
  2. Only one connection is on. Two active connections can duplicate leads.
  3. The right key was entered. Provider Key for Leads API, Open API Key for Pro API.
  4. Pro API only: your Open API level is Premium, not Basic (Basic is read-only).
  5. The card shows Connected — not Disabled or Connection Failed. Also check that Enable integration is checked on the Connection tab.
  6. The lead is waiting for real contact details. If Don't sync masked data from third-party lead sources is checked and the lead only has masked contact details, LeadTruffle waits instead of sending.
  7. Review the integration error shown in LeadTruffle for the specific reason.


If a lead landed in the wrong branch:


  • Confirm you're on the Pro API. The Leads API doesn't support branch routing.
  • Check the Branch routing tab for a mapping marked Needs attention. Its branch may no longer be available, so leads are going to your fallback instead.
  • Check that the lead's original Google LSA account is mapped. Unmapped accounts follow your When no Google LSA mapping matches setting.
  • Make sure you clicked Save changes after editing mappings. Changes only affect future submissions.


If you're seeing duplicate records, make sure only one LeadTruffle connection is on and no other tool is sending the same leads. See Using other tools that send leads to SmartMoving.



Need help? Contact us at support@leadtruffle.com or message the team via the chat on this article or in-app.

Updated on: 11/10/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!