How to Add Leads to Buying Buddy from GoHighLevel Workflow

Contents

Automatically sync your GoHighLevel contacts with Buying Buddy and set up listing alerts through webhook integration. This guide will walk you through the complete setup process.

Before You Begin: You'll need the following found in your Buying Buddy account:
Get your API Key: Menu Leads > Integrations and APIs (API tab)
Get the mls_id: Menu Widgets > Authorized Websites

Setup Steps

Configure the Webhook in GoHighLevel

Set up the HTTP request in your workflow

In your GoHighLevel workflow:

Add a new action and select Webhook
Set Method to POST
Enter the URL:

https://www.leadsandcontacts.com/api-lead/add

Add Required Fields

Configure essential contact information

Add these fields to your webhook configuration:

Field Name	GHL Value	Required
`api_key`	Your API Key	✓ Yes
`client_lead_id`	{{contact.id}}	Recommended
`first_nm`	{{contact.first_name}}	Recommended
`last_nm`	{{contact.last_name}}	Recommended
`email`	{{contact.email}}	Recommended
`phone`	{{contact.phone}}	Optional
`site_url`	Website Domain	Optional. Website domain (without www) for lead assignment in multi-domain accounts.

Important: Use first_nm and last_nm (not "first_name" or "last_name" or other variants)

Enable Listing Alerts (Optional)

Automatically create property alerts for leads

To create listing alerts for your leads, add these fields:

Field Name	Value	Notes
`listing_alert`	1	Required to set up listing alerts. Set to "1" to enable
`listing_alert_frequency`	daily	Options: instant, daily, weekly, monthly
`listing_alert_nm`	Custom name	Optional (defaults to "First Saved Search")

Critical: When enabling listing alerts (listing_alert = 1), you MUST include sf_mls_id in your search criteria!

Add Search Criteria Fields

Define property search parameters

Critical: ALL search fields MUST use the sf_ prefix! Example: Use sf_city not just city

Required MLS Field

Get "mls_id" from Authorized Websites shown your Buying Buddy account

sf_mls_id

Common Search Fields

Location

sf_city
sf_state
sf_county
sf_zip_code

Price

sf_price_min
sf_price_max

Property Type

sf_property_type
sf_property_subtype
sf_listing_status

Beds & Baths

sf_bedrooms_total_min
sf_bedrooms_total_max
sf_baths_total_min
sf_baths_total_max

Tip: For multiple values, separate with commas: sf_city = "Austin,Dallas,Houston"

Complete Configuration Example

Here's an example webhook configuration with all commonly used fields:

Add Buying Buddy lead_id to your Highlevel Contact

When the custom webhook is triggered, a response is sent back from the Buying Buddy API that includes the lead_id from the Buying Buddy system. It is recommended that you save this to the contact record in Highlevel.

The flow is:

Custom Webhook action (POST to Buying Buddy) → enable "Save response from this Webhook".
Update Contact action → map the captured lead_id reference into a custom field (e.g. "Buying Buddy Lead ID").

Setup detail

Create the custom field first. Add a contact custom field (text or number) for the Buying Buddy lead ID before you configure the Update Contact step, so it's available to map to.
In the Custom Webhook action check the option called "Save response from this Webhook," which captures the JSON response from the Buying Buddy API.
Test in draft mode to seed the response. To make the reference resolve to lead_id, the webhook needs to have actually run once and returned a sample so HighLevel knows the response shape. So, use Test Workflow (draft mode) with a sample record to trigger the action - this generates a real response so the lead_id key appears in the reference picker. Without a captured sample, you won't see the key to map.
Add Update Contact action that writes lead_id into a custom field on the contact.

Watch the response type. Your example returns "lead_id": 12345 as a number and "success": "true" as a string. That's fine for mapping, but if you ever branch on success, treat it as a string.

Example of the Add Lead API Response

{
    "success": "true",
    "code": "new",
    "msg": "Lead Imported Successfully",
    "lead_id": 12345
}

Testing Your Integration

Verify Your Setup

Follow these steps to test your webhook

Save your workflow in GoHighLevel
Run a test with a sample contact
Check Buying Buddy Menu Leads > Lead Summary to verify the lead was added
If you enabled listing alerts, check the lead details has the alert setup.

Success! If the lead appears in Buying Buddy, your integration is working correctly.

Problems? See the API Log to review what was received.

Troubleshooting Common Issues

Lead Not Appearing in Buying Buddy

Verify your API key is correct and active
Check the webhook URL is exactly: https://www.leadsandcontacts.com/api-lead/add
Ensure the method is set to POST
Check GoHighLevel workflow logs for error messages

Listing Alert Not Created

Ensure listing_alert is set to "1"
Verify sf_mls_id is included and correct
Check that at least one search criteria field is populated
Confirm the MLS ID matches one in your Authorized Websites

Search Fields Not Working

Remember ALL search fields must use the sf_ prefix
Double-check field names (e.g., first_nm not "first_name")
Verify values match your MLS options exactly
Test with basic fields first (city, price range)

Additional Resources

Widget Wizard: Discover all available search fields using the Wizard
API Documentation: Access full API reference in Menu Leads > Integrations and Apis
Support: Submit a ticket through Menu Help > New Ticket in your Buying Buddy account

Updated on August 10, 2026

Was this article helpful?

Yes No