How-to guide · You set it up
Send open house leads to Sierra Interactive
Sierra Interactive's Create Lead action demands more than any other CRM in this cluster: a last name, an email, and a password. Here is how to satisfy all three from an open house sign-in without the Zap failing on half your visitors.
Who is actually doing the connecting
You are. Open House Console does not plug into Sierra Interactive, 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 Sierra Interactive 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
Sierra Interactive's Zapier app has ten write actions, more than anything else here, and Create Lead is the entry point to all of them. It is also the fussiest: first name, last name, email and password are all required, which means three of the four have to be solved in the Zap before a real visitor ever hits it. Everything else on this page follows from those four required fields.
The Sierra Interactive 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.
4Split the name and give the last name a fallback
Both halves are required here, so the Formatter split is not optional the way it is for most of these. Add Formatter by Zapier, Text, Split Text on a space, map segment one to Lead First Name and segment two to Lead Last Name. Then handle the visitor who typed only Dana: in the Last Name field, use Zapier's default value so an empty segment becomes something harmless rather than failing the Zap. A lead named Dana Visitor is recoverable. A lead that never arrived is not.
5Filter out the sign-ins with no email, do not let them error
Email is required by this action, and our email field is empty whenever you have turned the email question off or a visitor left it blank. Add a Zapier filter step before the Sierra action so the Zap only continues when the email field is present. Without it, every phone-only sign-in becomes a failed task in your Zap history, and Zapier eventually turns the whole Zap off after enough of them. Send the filtered-out ones somewhere useful, an email to yourself or a row in a sheet, rather than nowhere.
6Put something in the Password field and leave registration email off
Sierra creates a website account for the lead, which is why Password is required. Type a fixed placeholder, or generate one with a Formatter step if you would rather each lead differ. Then leave Send Registration Email off. A visitor who filled in a sign-in sheet at a front door has not asked for a login on your website, and an unexpected account email an hour later is a strange first impression.
7Add the action plan as a second step, not as a checkbox
This is where Sierra differs from everything else in this cluster. Applying an action plan is its own action, Apply Fully Automated Action Plan or Apply Traditional Action Plan, added after Create Lead in the same Zap. That is more work and it is better: you can filter on it. Send the pre-approved visitor buying in three months into one plan and everyone else into another, using a Zapier path on our financing and timeframe fields.
Field mapping
What goes where in Sierra Interactive
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 | Lead First Name | Required. Segment two goes to Lead Last Name, also required. |
lead.email | Required. Filter the Zap on this or it fails on phone-only sign-ins. | |
lead.phone | Phone | |
open_house.address | Source | Or Site if you run separate Sierra sites per area. |
lead.financing_status | Note | Also worth branching a Zapier path on. |
lead.buying_timeframe | Note | The other half of the path condition. |
lead.custom_answers | Note | Question and answer pairs, in the same note. |
lead.has_agent | Tags | |
lead.home_to_sell_address | Street 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 Sierra Interactive
The email requirement is a real constraint on how you run the door, not just a Zap detail. If you have turned the email question off to keep sign-in fast, those visitors cannot reach Sierra through this action at all. Decide which you want before an event rather than during one.
Password being required means the Zap creates a site account for every lead. That is Sierra working as designed, but it is worth knowing before a visitor asks why they got a website login.
Ten write actions is enough rope to build something fragile. Create Lead plus one action plan step is the whole useful setup. Adding tasks and notes as further steps multiplies the ways a single Zap run can half-fail.
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 Sierra Interactive?+
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 Sierra Interactive, using your own Sierra Interactive 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 to a visitor who only gives a phone number?+
Sierra's Create Lead requires an email, so that visitor cannot go through this action. The filter step in the instructions is what stops them from failing your Zap. They are still saved in your Open House Console dashboard with their phone number, so nothing is lost; they just have to be called rather than routed.
Why does the action want a password?+
Sierra creates a site account for the lead as part of Create Lead. Supply a placeholder and leave Send Registration Email switched off, and the visitor never sees it.
Sierra Interactive 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