How-to guide · You set it up
Send open house leads to Lofty
Send every open house sign-in into Lofty as a new lead, with the buyer and seller details in the right halves of the record, using a webhook and your own Zapier account. Includes the part most setups get wrong: the consent boxes.
Who is actually doing the connecting
You are. Open House Console does not plug into Lofty, 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 Lofty 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 Lead
Lofty's Create Lead is the richest action in this cluster and the one that most rewards slowing down. It carries a buyer half and a seller half, a Segment, a Tag, a Note, subscription switches for Smart Plans, property alerts and market reports, and separate consent switches for calls, texts and email. Almost none of those are things we can fill in for you honestly, which is the actual lesson of this page.
The Lofty 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.
4Add Create Lead and map only what you were told
Add an action step, choose Lofty, pick Create Lead, and connect your account. Then work down the field list once and leave blank everything nobody answered. It is a long form and the temptation is to fill it in. A lead record that looks complete but is half guessed is worse than a thin one, because you will act on it.
5Leave the consent switches alone unless you actually asked
Create Lead has switches for call, text and email consent. Our sign-in form does not ask for texting consent unless you added a question that asks for it. If you did not ask, do not tick them, and do not map anything into them. Turning them on because the Zap offers them is you recording a consent that nobody gave. If you want that consent, add the question to your sign-in form first, then map that answer here.
6Send the seller half only when they said they have a home to sell
Lofty keeps buyer preferences and seller property details as separate blocks. We send home_to_sell as true or false and home_to_sell_address only when it is true. Add a Zapier filter or a path so the seller block is populated only on a yes, otherwise every buyer arrives looking like a listing appointment.
7Translate the timeframe before it reaches the timeframe field
Lofty has native timeframe fields on both the buyer and seller sides, which is genuinely useful, but our values are phrases like 0-3 months and Just browsing. If Lofty offers you a fixed list rather than a free text box, put a Formatter by Zapier step in between, Utilities, Lookup Table, and convert each of our four values to theirs. Skip this and the field either rejects the value or stores a string nothing filters on.
8Decide about Smart Plans deliberately
Subscribing every door visitor to a Smart Plan is the fastest way to get same-day follow-up out of this, and it is also the fastest way to send an automated sequence to someone who only wanted to see a kitchen. Turn it on for one specific plan you have actually read, or leave it off and call them yourself.
Field mapping
What goes where in Lofty
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 | First Name | After a Formatter split; segment two goes to Last Name. |
lead.email | ||
lead.phone | Phone | Stored as (512) 555-0148; convert if you text from Lofty. |
lead.buying_timeframe | Buyer timeframe | Through a Formatter lookup table if Lofty shows a fixed list. |
lead.home_to_sell_address | Seller property address | Behind a filter on home_to_sell being true. |
lead.financing_status | Note | There is no native financing field on this action. |
lead.custom_answers | Note | Question and answer pairs, in the same note. |
open_house.address | Source | Or a per-listing Tag if you run several at once. |
lead.has_agent | Tag | A visitor with an agent should not enter the same Smart Plan. |
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 Lofty
The consent switches are the one thing on this page that can cost you real money rather than a tidy database. Do not map them, and do not tick them by hand, unless your sign-in form actually asked the question and this visitor said yes.
Lofty was called Chime, and older help articles and forum answers still use that name. The Zapier app is listed as Lofty. If a search result shows you a Chime setup screen, it is describing the same product under its old name.
Create Lead and Create Transaction are separate actions. Nothing about an open house sign-in belongs in a transaction, so ignore that half of the app no matter how tempting the pipeline fields look.
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 Lofty?+
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 Lofty, using your own Lofty 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.
Should I tick the text consent box so I can text these visitors?+
Only if you asked them and they said yes. The switch is there for leads who gave consent somewhere it was collected properly. Ticking it because a form offered it does not create consent, it just records one you do not have. Add a consent question to your sign-in form and map that answer instead.
Is this different for Chime?+
Chime is the former name of the same product. The Zapier app is listed under Lofty, and the actions and fields described here are the ones that app exposes today.
Lofty 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