This Solution Guide shows how to run your business with Buying Buddy and HighLevel working together. Buying Buddy is the property engine - live MLS search on your site, lead registration, saved searches, New Listing Alerts and Market Reports. HighLevel is your CRM - contacts, pipeline, nurture, SMS and appointments. Below you will find the recommended split of responsibilities, the pages to build, a worked example of a lead moving through both systems, which webhook events to send, and the pitfalls to avoid.
Looking for click-by-click setup? This guide explains how the two systems should work together. For the installation and connection steps, follow Getting Started with Buying Buddy on HighLevel, which links to each detailed guide in order.
The recommended model
Each system does what it is best at, and webhooks keep HighLevel up to date with what your leads do in Buying Buddy. HighLevel stays your CRM of record - the place your team works every day.
| Job | Handled by | Why |
|---|---|---|
| Property search, listing results, maps and property details on your site | Buying Buddy | Live data from your MLS feed, displayed to your MLS rules |
| Lead registration on your website | Buying Buddy | Captures search behavior from the first visit |
| Saved searches and New Listing Alerts | Buying Buddy | Sent automatically as matching listings come on the market |
| Market Reports | Buying Buddy | Built from your MLS data and kept up to date |
| Lead activity tracking and lead score | Buying Buddy, sent to HighLevel by webhook | Your automations run on real search and property activity |
| Contact record, tags and pipeline | HighLevel | One place for your whole database |
| Nurture campaigns, SMS and calls | HighLevel | Your existing workflows and messaging |
| Appointments and agent tasks | HighLevel | Triggered by Buying Buddy events such as a showing request |
Let one system send property emails. Buying Buddy sends New Listing Alerts and Market Reports. Do not also build property-listing emails in HighLevel for the same leads, or they will receive duplicates. Use HighLevel for your personal follow-up, SMS and non-property nurture.
Recommended pages on your HighLevel site
Build these pages in your HighLevel site or funnel and place the Buying Buddy widgets on them. The install guides show exactly how to add widgets in the standard HighLevel builder and in HighLevel AI Studio.
| Page | What goes on it | Why it matters |
|---|---|---|
| Home page | A quick search form and a featured listings gallery | Gets visitors searching straight away |
Listing results (for example /listing-results) | The search results widget | Required - every search lands here |
Listing details (for example /listing-details) | The property details widget | Required - this is where visitors save homes, request showings and ask for more information |
| Neighborhood or community pages | Listings filtered to that area | Strong pages for search traffic and ads |
| Home value or market page | A Market Report widget | Captures seller and homeowner leads |
Install guides: Install Buying Buddy on HighLevel and Install Buying Buddy on HighLevel AI Studio. To see every widget available, visit Published IDX Widget Set.
How a lead moves through both systems
Here is a worked example. Jordan finds your website from a Facebook ad and starts searching for 3-bedroom homes. Each step shows what Jordan does, the Buying Buddy webhook event it sends, and a suggested HighLevel action.
1
Jordan registers on your site
Event: lead.created
Jordan registers to see more listings. Buying Buddy creates the lead and sends lead.created to HighLevel.
In HighLevel: create or update the contact, add a tag such as bb-website-lead, save the Buying Buddy lead_id and lead_url to custom fields, and start your new-lead nurture.
2
Jordan saves a search
Event: lead.saved_search
Jordan saves "3 bed under 450k" with daily alerts. From now on Buying Buddy emails Jordan matching new listings automatically.
In HighLevel: add a tag such as active-searcher and save the search name and alert frequency to custom fields, so your agent knows what Jordan wants before the first call.
3
Jordan keeps coming back to one home
Event: lead.listing_viewed_3
Jordan views the same property for the third time - a strong buying signal. The event includes the property address, price and link.
In HighLevel: create a task for the agent ("Call Jordan about 2801 Eppinger Blvd") or send a short SMS offering a showing.
4
Jordan requests a showing
Event: lead.schedule_showing
Jordan clicks Schedule a Showing on the property details page. The event includes the property and everything Jordan typed on the form, such as a preferred time.
In HighLevel: create or move an opportunity to a "Showing requested" pipeline stage, notify the assigned agent, and send a confirmation SMS.
5
Jordan unsubscribes from email
Event: lead.optout
If Jordan clicks unsubscribe in a Buying Buddy email or marks one as spam, Buying Buddy stops all email to Jordan and sends lead.optout.
In HighLevel: set Do Not Disturb for email on the contact so your HighLevel campaigns respect the same choice.
Choosing which events to send
You choose events in Buying Buddy at : click Get started on the HighLevel card, pick an event from the Add a trigger... list, paste the HighLevel webhook URL and click Add. Full steps are in Webhook Setup Guides.
| Event | When it fires | Suggested HighLevel action | Set |
|---|---|---|---|
lead.created | A new lead registers or is imported | Create or update contact, tag, start nurture | Starter |
lead.schedule_showing | Lead requests a showing | Pipeline stage, notify agent | Starter |
lead.request_info | Lead asks for more information on a property | Task for agent | Starter |
lead.request_contact | Lead asks to speak with an agent | Task or call assignment | Starter |
lead.form_submitted | Lead submits any other form | Route by form fields | Starter |
lead.optout | Lead unsubscribes from all email | Set email Do Not Disturb | Starter |
lead.saved_search | Lead saves a search | Tag and save search details | Full |
lead.saved_listing | Lead saves a property | Note or tag | Full |
lead.listing_viewed_3 | Lead views the same property 3 times | Hot-lead task or SMS | Full |
lead.login | Lead logs back in | Update a "last active" field | Full |
lead.send_friend | Lead shares a property | Note on contact | Full |
lead.lead_assigned | Lead is assigned to an agent | Match the contact owner | Full |
For every field each event sends, see Webhook Data Reference.
Each event is a billable workflow run. Every event Buying Buddy sends runs your HighLevel workflow once, and HighLevel bills each run. Start with the Starter set and add the Full set events once you have a clear action for each one.
One workflow per event, or one for all
Both work. The simplest approach is one HighLevel workflow per event, each with its own Inbound Webhook URL, so each workflow does one job. Alternatively, send several events to one workflow and add an If/Else step that branches on the event field (for example event is lead.schedule_showing). Either way, after adding the URL in Buying Buddy, use the Send Test button (the paper plane) and then Fetch Sample Requests in HighLevel so the fields are available to map.
Fields worth saving on the HighLevel contact
Create these contact custom fields in HighLevel and map them from the webhook data. They give your team context without opening Buying Buddy.
| Webhook field | Suggested custom field | Why |
|---|---|---|
lead_id | Buying Buddy Lead ID | Links the two records permanently |
lead_url | Buying Buddy Profile | One click from HighLevel to the lead's full search and property activity |
lead_score and lead_temperature | BB Lead Score, BB Temperature | Prioritize calls and build smart lists |
leadsource_nm | BB Lead Source | Shows how the lead came in, and helps prevent loops (see below) |
search_nm and frequency (saved search events) | Saved Search, Alert Frequency | What the lead is looking for |
property_url (property events) | Last Property Viewed | Talking point for the next call |
Sending HighLevel contacts to Buying Buddy
The reverse direction is just as useful. When a contact enters HighLevel from somewhere else - a Facebook lead ad, an open house sign-in, a purchased list - a HighLevel workflow can send it to Buying Buddy and set up New Listing Alerts in the same step. The contact then gets listing emails from day one and their activity flows back to HighLevel.
Follow How to Add Leads to Buying Buddy from a HighLevel Workflow. Always include client_lead_id set to {{contact.id}} so Buying Buddy stores the HighLevel contact ID with the lead.
Market Reports: contacts sent from HighLevel can be set up with New Listing Alerts automatically. Market Reports are set up from your Buying Buddy dashboard.

Avoid the round-trip loop
Important if you send leads in both directions
When HighLevel sends a contact to Buying Buddy, Buying Buddy creates a new lead - and if you send lead.created to HighLevel, that contact comes straight back into your new-lead workflow. Each round trip is a billable workflow run and can restart nurture for someone already in it.
Leads that arrive from HighLevel are easy to recognize in the lead.created data: leadsource_nm is API Import and client_lead_id holds the HighLevel contact ID.
To stop the loop:
- In HighLevel, open the workflow that receives
lead.created. - Directly after the Inbound Webhook trigger, add an If/Else step.
- Set the condition to:
client_lead_idis not empty (orleadsource_nmis API Import). - On the matching branch, either end the workflow or only update the contact's Buying Buddy fields. Put your new-lead actions on the other branch.
Result: website registrations still start your new-lead nurture, while contacts that came from HighLevel just get their Buying Buddy ID and profile link saved.
Keep your team working in HighLevel
Embed your Buying Buddy dashboard as a page inside HighLevel so agents can manage leads, New Listing Alerts and Market Reports without switching apps. See Embed Your Buying Buddy Dashboard in Another Platform. Combined with the lead_url custom field, any contact is one click from its full Buying Buddy history.
What does not sync today
So you can plan around them, these are not sent to HighLevel at present:
- Alert and report engagement - there is no event when a New Listing Alert or Market Report is opened or clicked.
- Lead edits - changes made to a lead inside Buying Buddy (contact details, status) do not send an event.
- Score and temperature changes -
lead_scoreandlead_temperatureare included in every event, but there is no separate event when a lead turns hot. - Market Reports from HighLevel - a HighLevel workflow can set up New Listing Alerts, but not Market Reports.
We are working to add more webhooks. Let us know which other events you want sent to your CRM - open a help ticket from your Buying Buddy dashboard and tell us the event and what you would do with it in HighLevel.
Launch checklist
- Search widgets installed, with working listing results and listing details pages.
- Buying Buddy dashboard embedded in HighLevel.
- Starter set of events connected and tested with Send Test.
- Custom fields created and mapped, including Buying Buddy Lead ID and Profile link.
- If sending contacts from HighLevel to Buying Buddy:
client_lead_idincluded and the loop filter added to your new-lead workflow. - Property-listing emails sent only by Buying Buddy.
- A test registration on your live site arrives in HighLevel with the right tags and fields.