How-to guide · You set it up
Send open house leads to kvCORE
Get every open house sign-in into kvCORE as a contact, tagged and attributed to the door rather than to a portal, using a webhook and your own Zapier account. Fifteen minutes, once, and it runs at every open house after that.
Who is actually doing the connecting
You are. Open House Console does not plug into kvCORE, 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 kvCORE 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 Contact (Post)
kvCORE's Zapier app is deliberately small: Create Contact (Post) and Update Contact, and that is the whole write surface. For a door sign-in you want the create. The consequence of that small surface is that this setup lives or dies on three fields most people leave blank, Source, Tags and Note, because there is nowhere else for a qualifying answer to go.
The kvCORE 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 Contact (Post) and connect your account
Add an action step, choose kvCORE, and pick Create Contact (Post). Zapier asks for your kvCORE credentials when you connect, and that connection lives in your Zapier account. If several people share your kvCORE account, connect as yourself so the audit trail in kvCORE points at a real person.
5Set Source and Form or Capture Method as fixed text
This action has Source, Secondary Source, and Form or Capture Method, and none of them should be mapped to one of our fields. Type them: Source as something stable like Open House, Form or Capture Method as something like Open house sign-in. Attribution is the single thing most agents lose when leads arrive by automation, and typing three words now is what lets you answer where these came from later.
6Put one stable tag on every door lead
Tags (Multiple) takes a list. Use one tag, spelled identically every time, on every lead this Zap creates. That one habit is what makes the whole season of open house traffic findable as a group in kvCORE instead of scattered among portal leads. Add a second tag for the property if you run several listings at once.
7Decide who owns the lead before you turn it on
Assign to Agent Email and Assign to Agent ID are on this action for a reason. Leave them blank and the contact is routed by whatever rules your kvCORE account already has, which on a team account may not be the agent who actually stood in the house. If the host should own the lead, type their email here, and remember to change it if someone else covers a weekend.
Field mapping
What goes where in kvCORE
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 | Optional here, so a phone-only sign-in still saves. | |
lead.phone | Cell Phone 1 | It is the number they typed at the door, so it is a mobile. |
lead.home_to_sell_address | Primary Address - Street | Their own home, not the listing. Only present when they said yes. |
lead.financing_status | Note | Combine with the two fields below into one note. |
lead.buying_timeframe | Note | There are no custom fields on this action. |
lead.custom_answers | Note | Question and answer pairs, readable as text. |
open_house.address | Note | Name the open house in the note so the contact record says where you met. |
lead.has_agent | Tags (Multiple) | Worth its own tag: a visitor with an agent is a different call. |
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 kvCORE
Do not map the listing address into the Primary Address fields. Those describe where the contact lives, and filling them with the open house address gives you a database of people who all appear to live in your listing. The listing belongs in the Note, and the visitor's own address belongs in Primary Address only when they told you they have a home to sell.
There are no custom field slots on this action, so financing and timeframe cannot be filtered on the way they can in Follow Up Boss or Top Producer. If filtering matters more than tidiness, spend a tag on it: one tag per timeframe bucket is ugly and it works.
Interested in City, Interested in Price and Interested in MLS# look inviting and we send nothing that belongs in any of them. Leave them empty rather than inventing a value, because a wrong price on a contact is worse than a blank one.
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 kvCORE?+
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 kvCORE, using your own kvCORE 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.
Can I have the lead assigned to whoever hosted the open house?+
Yes, by typing that person's email into Assign to Agent Email. It is a fixed value in the Zap rather than something we send, so if a different agent covers a Sunday you have to change it, or accept that the lead lands on whoever the Zap names.
Where do my custom sign-in questions end up?+
In the Note, as question and answer pairs. kvCORE's Zapier action has no custom fields, so the note is the only place they can be read in full. Anything you need to search on later should also become a tag.
kvCORE 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