How-to guide · You set it up
Send open house leads to Follow Up Boss
Every visitor who signs in at your open house can land in Follow Up Boss as a real inquiry, with their financing and timeframe answers attached, using a webhook and your own Zapier account. Roughly fifteen minutes to set up, once.
Who is actually doing the connecting
You are. Open House Console does not plug into Follow Up Boss, 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 Follow Up Boss 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 New Inquiry or Website Event
Follow Up Boss gives you two ways to create a person, and the difference matters more here than anywhere else in this cluster. Create Contact Without Triggering Action Plans does exactly what it says: the visitor appears, and nothing happens. New Inquiry or Website Event files them the way a lead from your website arrives, so your lead flow, your action plans and your notifications all behave as they already do. It is also the only one of the two that carries custom field slots, which is the only place the sign-in answers survive as data you can filter on.
The Follow Up Boss 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.
4Pick the action, and understand what you are giving up
Add an action step, choose Follow Up Boss, and pick New Inquiry or Website Event. The trade is worth knowing before you commit: the other action, Create Contact Without Triggering Action Plans, has a native Timeframe field and this one does not. This one has five custom field slots and fires your automation. For a door sign-in that you want called the same evening, the automation is worth more than the tidy field, and the timeframe still lands, just in a custom field instead.
5Fill in Event Type, which is the only required field
Zapier shows you the event types your account accepts. Pick the one that reads correctly in the contact's timeline six months from now, and use the same one every time so these are filterable as a group. Everything else on this action is optional, which means a phone-only sign-in still works.
6Split the name, because Follow Up Boss wants two
We send one name field, exactly as the visitor typed it. Add a Formatter by Zapier step, Text, Split Text, separator space, then map segment one to First Name and segment two to Last Name. Neither is required here, so a visitor who typed only Dana still saves rather than erroring the Zap.
7Name your custom fields once, then map the answers
The action takes five pairs: Custom Field 1 Name and Custom Field 1 Value, and so on. Type the names as literal text, the same wording every time, and map our answers into the values. Change the wording later and you get a second field in Follow Up Boss holding half your history, so decide the labels now.
Field mapping
What goes where in Follow Up Boss
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 | Email Address | Empty when you have turned the email question off. |
lead.phone | Phone Number | Arrives as (512) 555-0148, not +1512. |
open_house.address | Street Address | The property they walked into, not where they live. |
lead.custom_answers | Message | Lands as readable text on the inquiry itself. |
lead.financing_status | Custom Field 1 Value | Name the field Financing. |
lead.buying_timeframe | Custom Field 2 Value | Name the field Timeframe. |
lead.has_agent | Custom Field 3 Value | Arrives as true or false. |
lead.home_to_sell | Custom Field 4 Value | Name the field Has a home to sell. |
lead.home_to_sell_address | Custom Field 5 Value | Only present when they answered 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 Follow Up Boss
Forwarding email will not work here. Follow Up Boss publishes a lead email address that parses notifications from sources it recognises, and we are not one of them. We also send one summary email per open house rather than one per visitor, so there is nothing per-lead to forward even if the parser knew us. Zapier is the path.
Type your source as fixed text rather than mapping a field to it. Every lead from this Zap has the same source, and that is the point: it is how you separate door traffic from portal traffic in your reporting later.
A visitor who pre-registers on your property page and then signs in again at the door fires the webhook twice, on purpose. That is two inquiries on one person, which is usually what you want on a timeline. If it is not, add a Zapier filter on the open house id.
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 Follow Up Boss?+
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 Follow Up Boss, using your own Follow Up Boss 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.
Will my action plans fire for open house leads?+
With the New Inquiry or Website Event action, yes, the same way they do for a lead off your website. That is the whole reason these steps use that action instead of the other one. If you would rather they did not, use Create Contact Without Triggering Action Plans and the visitor lands quietly.
What happens to the answers to my own custom sign-in questions?+
They arrive as a list of question and answer pairs. Mapped into the Message field they read as plain text on the inquiry. If one specific question matters enough to filter on, give it its own custom field slot instead.
Follow Up Boss 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