How-to guide · You set it up
Send open house leads to BoomTown
BoomTown's single write action creates or updates in one move, which quietly solves the duplicate problem the other CRMs make you solve by hand. Here is the field map, in the raw field names the action actually shows you.
Who is actually doing the connecting
You are. Open House Console does not plug into BoomTown, and this page is not an announcement that it does. We post every new sign-in to whatever URL you give us. You catch it in your own Zapier account, with your own BoomTown login, and you decide where each field lands. Nobody has to approve anything, which is exactly why this works with a CRM that has never heard of us.
Why Create or Update Lead
BoomTown exposes exactly one write action, and it is an upsert: Create or Update Lead creates a new lead or updates an existing one in the same step. That single design decision is why this page reads differently from the rest. Everywhere else you have to decide what happens when the same visitor arrives twice. Here you do not.
The BoomTown app on Zapier (opens in a new tab). Checked on 2026-08-29. Action names and fields on this page come from that listing, not from us.
Step by step
Setting it up, start to finish
The first 3 are the same for every CRM. The rest are specific to this one.
1Start a Zap with Webhooks by Zapier
In your own Zapier account, create a Zap and choose Webhooks by Zapier as the trigger, then the Catch Hook event. Zapier gives you a URL that is yours alone. Nothing here runs through us, and your CRM login never leaves your Zapier account.
2Paste that URL into your profile
Open your Open House Console dashboard, go to Profile, and paste the URL into the CRM / Zapier field. Save. From that moment, every visitor who signs in at any of your open houses is posted to that address as JSON, in the background, without slowing down the screen in front of them.
3Do one test sign-in so Zapier learns the shape
Open your own sign-in page and fill it in as if you were a visitor, answering every question you have turned on. Zapier catches that first lead and uses it to build the list of fields you can map. Skipping a question here means Zapier never sees that field and you cannot select it later, so answer them all, then delete the test lead from your dashboard.
4Expect raw field names, and read them once before you map
Add an action step, choose BoomTown, and pick Create or Update Lead. The fields come through with their underlying names, firstName, emailAddress, zipCode, rather than the friendly labels most Zapier apps show. Nothing is wrong. Read the list once so you are not hunting for a field called Email that is spelled emailAddress.
5Split the name, and give lastName a default
firstName and lastName are the only two required fields. Add Formatter by Zapier, Text, Split Text on a space, and set a default value on the lastName mapping so a visitor who typed one word does not fail the run. This is the same fix Sierra Interactive needs, and for the same reason, but here it is the only requirement you have to work around rather than the first of four.
6Use Day Phone, and leave the other two alone
There are three phone fields: Day Phone, Night Phone and Phone 3. We send one number, typed on a phone at a front door, so it belongs in Day Phone. Do not copy it into all three to look thorough. A record with the same number in three fields is a record nobody trusts.
7Put everything else in notes, and keep description for yourself
notes and description are separate fields. Send the open house address, the financing and timeframe answers, and your custom question answers into notes as one block. Leave description empty, or use it for your own one-line summary after you have spoken to them. Two fields doing the same job is how a CRM stops being readable.
Field mapping
What goes where in BoomTown
Left is what we send. Right is the field on that action, named the way it names itself.
| We send | Put it in | Watch for |
|---|---|---|
lead.name | firstName | Required. After a Formatter split; segment two goes to lastName. |
lead.email | emailAddress | Optional here, so phone-only sign-ins still save. |
lead.phone | Day Phone | One number, one field. Leave Night Phone and Phone 3 empty. |
open_house.address | notes | The only place the words open house can land on this action. |
lead.financing_status | notes | |
lead.buying_timeframe | notes | Same block, so it reads as one paragraph. |
lead.custom_answers | notes | |
lead.has_agent | notes | Put it on its own line at the top. It changes the call. |
lead.home_to_sell_address | address | Their own home. Only present when they said yes. |
Every field except the name, the open house and the timestamp can be empty, because you choose which questions your sign-in form asks.
Before you turn it on
What goes wrong with BoomTown
This action has no Source field, so there is no way to attribute a lead to the door through the field map alone. The words have to go in notes, and if you want them filterable you have to tag the lead inside BoomTown afterwards. That is a real limitation of the action, not something a better Zap fixes.
closingDate and avgListingPrice are on the action and we send neither. Leave them blank. A guessed average listing price will end up in a report one day and be treated as a fact.
The upsert matches on what BoomTown decides matches, not on anything you control from the Zap. That is usually what you want, but it does mean two visitors who share a household email can merge into one lead.
Reference
Exactly what we post
One of these arrives the moment a visitor finishes signing in, in the background, once per sign-in.
{
"event": "lead.created",
"lead": {
"name": "Dana Whitfield",
"email": "dana.whitfield@example.com",
"phone": "(512) 555-0148",
"has_agent": false,
"financing_status": "Pre-approved",
"buying_timeframe": "0-3 months",
"home_to_sell": true,
"home_to_sell_address": "1140 Cedar Bend Dr",
"custom_answers": [
{
"question": "How did you hear about this open house?",
"answer": "The sign on the corner"
}
]
},
"open_house": {
"id": "6f0a1c8e-2b77-4c1e-9a0b-3d5e7f911c24",
"address": "482 Maple Ridge Ln, Austin, TX 78704"
},
"captured_at": "2026-08-29T21:04:11.302Z"
}Two details catch people out. The name is one string, exactly as the visitor typed it, so a CRM that wants a first and a last name needs a Formatter step in between. And the phone arrives formatted the way we store it, as (512) 555-0148, so anything that expects the plus-one form needs converting too.
Your CRM is the destination, not the system of record. Every lead is still in your Open House Console dashboard with its notes and follow-up status, so a Zapier task that fails at midnight cannot lose you a visitor.
FAQ
Common questions
Does Open House Console plug into BoomTown?+
No, and nothing on this page says it does. Open House Console posts every new sign-in to whatever URL you put in your profile. You are the one who catches it in your own Zapier account and points it at BoomTown, using your own BoomTown login. Neither company has to agree to anything, which is precisely why this works today rather than waiting for two software companies to find time to talk.
What happens if the same visitor signs in twice?+
Create or Update Lead updates the existing record instead of making a second one. That is the main practical advantage BoomTown has here, and it matters because a visitor who pre-registers on your property page and then signs in again at the door genuinely does fire our webhook twice.
Why are the field names written oddly?+
They are the underlying API names rather than display labels. emailAddress is the email field, zipCode is the postcode, and so on. It looks like a bug the first time and it is just how this action presents itself.
BoomTown changed something and this page is now wrong? Tell us and we will fix it or take the page down. support@openhouseconsole.com
Other CRMs
Using something else?
Same webhook, different fields at the far end.
Back to every CRM walkthrough →
Keep reading
Free open house guides
Written by working agents. No signup, no email, nothing to download.
Or read the open house blog →
Capture the lead first. Routing it is the easy part.
Open House Console runs the sign-in on a laptop at the door, or on a phone the visitor already has in their hand, then hands the lead to your dashboard and to whatever URL you point us at. Free for 7 days.
Nothing charged today · or log in