For Builders: How to Send New Home Buddy Leads to Your CRM with Zapier

No developer needed. About 30 minutes.

New Home Buddy sends you leads the second a buyer acts on one of your homes.

We deliver those leads two ways. You get an email, and we post the lead to a URL you give us. That second part is where builders get stuck.

Some systems accept our lead post directly. Salesforce is one. You hand us a URL, you hand us a header, and you’re done.

Other systems don’t work that way. Lasso is the big one. Lasso wants leads created through its own app connection, not through a raw JSON post.

Zapier solves this. It sits between us and your CRM and translates.

You don’t need a developer for this. You don’t need to read an API doc. You need about 30 minutes and an API key from your CRM rep.

Let’s walk through it.

IN THIS ARTICLE

Jump to Section

Before You Start

Step 1: Create the Zap

Step 2: Copy Your Webhook URL

Step 3: Send the URL to New Home Buddy

Step 4: Test the Trigger

Step 5: Learn The Field Names

Step 6: Figure Out Whose Lead It Is

Step 7: Send the Lead to Your CRM

Step 8: Turn the Zap On

Tips for Working the Dashboard Into Your Routine

First, Don’t Go Looking For Us in Zapier

Open Zapier and search the app directory for “New Home Buddy.” You won’t find us.

That’s expected. We’re a young company and we haven’t published a Zapier app yet.

It doesn’t block you. Zapier has a built-in tool called Webhooks by Zapier that catches data from any system, listed or not. That’s the method in this guide.

You’ll sometimes hear it called a custom webhook. Same thing.

Before You Start

Gather four things.

  1. A Zapier account on the Professional plan or higher. Zapier lists webhooks as unavailable on Free. Webhooks is a premium app, so the free plan won’t run it. Check zapier.com/pricing before you buy, since tiers change. Zapier gives you a 14-day trial of premium features if you want to test first.
  2. Your CRM credentials. Lasso users need a Project Name and an API Key. Contact your Lasso Client Director and ask for the Zapier integration key. Keys are tied to a single project, so ask for one per community if you sell in several.
  3. A decision on lead routing. Do all New Home Buddy leads go to one place? Or do agent leads and buyer leads go to different people? Decide now. It’s easier than reworking it later.
  4. Our email address. Send setup requests to support@newhomebuddy.com.

Step 1: Create the Zap

Log in to Zapier. Click Create, then Zap.

For the trigger app, search Webhooks by Zapier.

For the trigger event, choose Catch Hook. Click Continue.

Zapier asks you to “Pick off a Child Key.” Leave that blank. We want the whole payload.

Step 2: Copy Your Webhook URL

Zapier now shows you a long URL. It looks something like this:

https://hooks.zapier.com/hooks/catch/1234567/abcdefg/

That URL is your lead delivery URL. Copy it.

Treat it like a password. Anyone who has it can push data into your CRM. Don’t paste it in a public place.

You won’t need custom headers for this. The random part of the URL is the security.

Step 3: Send the URL to New Home Buddy

Email support@newhomebuddy.com with two requests.

First, ask us to set that URL as your lead delivery URL.

Second, and this matters, ask us to send you test leads. Zapier can’t map fields it has never seen. It needs a real sample.

Ask for these four:

  • A Request Tour lead (a specific home, with an address)
  • A Request Details lead (a plan in a community, no address)
  • A Buyer Needs Request
  • A connection-forwarded lead to one of your sales reps

We do this for builders all the time. Just ask.

Step 4: Test the Trigger

Once we confirm we’ve fired the tests, go back to Zapier.

Click Test trigger.

Zapier pulls in the requests it caught. Pick one and click Continue.

Do this soon after we tell you the tests are out. Zapier only shows the three most recent webhooks from the past hour. Wait until tomorrow and the samples are gone.

If Zapier finds nothing, the URL didn’t reach us or the test hasn’t run yet. Email us and we’ll check the delivery log on our side.

Step 5: Learn the Field Names

Our payload has nested sections. Zapier flattens them using double underscores.

Here’s what you’ll be mapping:

What it isZapier Field Name
First nameformData__firstName
Last nameformData__lastName
EmailformData__email
PhoneformData__phone
Is this an agent?formData__isRealtor
MessageformData__message
BrokerageformData__brokerageName
Tour dateformData__tourDate
Plan namehome__planName
Street addresshome__address__address1
Cityhome__address__city
Communityhome__builderCommunityName
Where it came fromnhb__portal / nhb__source

Two notes on formatting.

Phone numbers arrive as 10 digits with nothing else. You’ll see 2105550100, not (210) 555-0100. Add a Formatter step if your CRM wants it pretty.

Tour dates arrive in UTC. A 3:00 PM Central tour shows as 20:00 or 21:00. Use a Formatter step to convert to your local time zone.

Step 6: Figure Out Whose Lead It Is

This is the step people skip, and it’s the one that saves you headaches.

A New Home Buddy lead can belong to three different people. The buyer’s contact info only reaches you when someone submits on a public search page with no agent involved. Otherwise we protect the agent’s buyer and send you the agent instead.

Use these three rules:

formData__isRealtor is true. The lead is a real estate agent. You’ll also get their brokerage name.

isRealtor is false and the message is a sales.newhomebuddy.com link. The lead belongs to one of your own sales reps. An agent they’re connected to has a buyer interested. That link opens the lead inside your rep’s New Home Buddy portal.

isRealtor is false and the message is regular text. That’s a buyer from public search.

Add a Filter step if you only want one type. Add Paths if you want to route each type differently.

Want to keep it simple? Skip this step for now. Send everything to one place and use nhb__portal as your lead source. You can add routing later.

Step 7: Send the Lead to Your CRM

Add an action step.

If you use Lasso: Search for LassoCRM in the app list. Choose the action that creates a registrant. Zapier asks you to sign in with your Project Name and API Key. That’s the key your Client Director gave you.

Now map the fields. Drag formData__firstName into First Name, formData__email into Email, and so on.

Set your lead source to something like “New Home Buddy.” You’ll want to report on it later.

If your CRM has a Zapier app: Same idea. Search for it and map the fields.

If it doesn’t: Add Webhooks by Zapier as the action and choose Custom Request. Then paste in your CRM’s endpoint and API key. This is the only step that gets technical, and your CRM’s support team can hand you the exact values.

Step 8: Turn the Zap On (The Last Step That’s Easy to Miss)

Building the Zap does not make it live. Go slow here.

Publish it

Click Publish in the top right of the Zap editor.

Is the Publish button greyed out? Then a step isn’t finished. Zapier makes you test every step before it lets you publish. Go back and click through each one until they all show a green check.

Confirm it’s on

Click Zaps in the left sidebar. Find your Zap in the list.

Look at the toggle next to it. It must say On. Don’t trust your memory. Look at the toggle.

Prove it works

Email us and ask for one more test lead. Then open your CRM and find the record.

A record in your CRM is the only proof that counts. Not our delivery log. Not a green check in the Zap editor. The record.

Why “it looked fine” isn’t good enough

Here’s the trap that caught the builders before you.

When your Zap is off, Zapier eventually returns a 404 to us. But that switch isn’t instant. Zapier warns of a system update delay of up to several hours. During that window, a turned-off Zap still answers with a 200.

We read a 200 as delivered. So our log says success, your Zap sits off, and the leads go nowhere.

Hours later the 404 kicks in and deliveries start visibly failing. By then you’ve lost a day of leads.

And we don’t retry. A lead we couldn’t hand off is gone from the pipe. You’ll still see it in your New Home Buddy portal and in your email, so nothing is truly lost. But your CRM won’t have it.

That’s why you check the CRM.

Two ways it turns itself back off

You edited it. Any change to a live Zap creates a draft. Your edits do nothing until you click Publish again. Zapier shows a banner about unpublished changes. Read that banner.

Zapier switched it off. If nearly all of your Zap’s runs fail over a week, Zapier turns the Zap off by itself. It stays off until a person turns it back on. Watch your error emails.

Open Zap History in Zapier every few days for the first month. Turn on Zapier’s error notification emails while you’re in there.

Five Things That Trip People Up

One submission can create several leads. If an agent is connected to more than one of your reps, we post the lead to each of them. That’s by design. If duplicates bother your team, dedupe on email plus home address.

Empty fields are normal. First name, email, and phone can all come through as empty strings when a visitor skips them. Don’t make those required in your CRM.

Buyer Needs Requests have no home. There’s no home block at all, so home__planName will be blank. Don’t build a step that requires it.

Changing the Zap URL means telling us. If you rebuild the Zap, you get a new URL. Email us the new one or leads stop arriving.

The URL belongs to a person, not your company. Your webhook URL contains the Zap owner’s Zapier ID. Transfer the Zap to a different user and the URL changes, so leads stop. Build this under a shared or role-based account, not the personal login of someone who might leave.

That’s It

You now have a live pipe from New Home Buddy into your CRM. Every tour request, plan inquiry, and connection-forwarded lead lands where your team already works.

No developer. No custom code. Just a webhook and a few field mappings.

Need help getting started? Email support@newhomebuddy.com and we’ll set up your delivery URL and fire the test leads.