AI Studio Vibe-Code Websites → GHL Sub-Account Webhook Lead Pipeline

Open AI Studio (Lovable), describe the offer in natural language ('Let's build a landing page for a Kentucky cash-home-buyer'), and iterate on hero, form, testimonials, and CTA sections in minutes. The page is React + Tailwind under the hood, mobile-first, brand-matched, and deployable in one click. This is the fast, low-friction front-end.

The form fields aren't arbitrary — they're chosen to match what GHL will need later (full name, phone, email, property address, city/state/zip, timeline, motivation, source, utm parameters). Naming them consistently up-front means the GHL workflow can map them 1-to-1 without transformation code.

Publish the AI Studio site to a subdomain (e.g. go.bluepathrealty.com). Wire the form's submit handler to POST the payload as JSON to a webhook URL we'll create in the next step. This decouples the site from the CRM — the site can be rebuilt or replaced without touching the automation.

Inside the client's GoHighLevel sub-account → Automation → Create Workflow → Trigger: Inbound Webhook. GHL generates a unique webhook URL. This URL is the doorway every external lead source will use.

This is what most people get wrong. When the payload has to write to a specific GHL sub-account (create contacts, tag them, add to opportunities), you can't just call any endpoint — you must authenticate with the sub-account's API token and pass the sub-account's Location ID. I generate a Location-scoped token inside the sub-account settings, store it as a server-side secret, and include it in the webhook call headers so every write lands in the correct account with the correct permissions. Wrong token = 401. Missing location ID = data lands in the wrong sub-account. This step is the reason clients hire me.

The workflow parses the incoming JSON into GHL Custom Values (custom_value.property_address, custom_value.source, custom_value.utm_campaign, etc.) and maps them onto standard + custom contact fields. Dedupe by email + phone: if the contact exists, update; otherwise create. No duplicates, full history preserved.

Based on utm_source, utm_medium, utm_campaign and the form's own 'source' field, the contact is auto-tagged (facebook-ad, google-ad, seo-organic, referral-partner, portal-import, etc.). These tags drive downstream routing — which pipeline, which nurture, which team member.

The workflow creates an Opportunity in the correct pipeline at the correct entry stage based on the tag. Cash-buyer leads land in the Acquisitions pipeline (Stage: New Lead). Seller leads land in the Seller Intake pipeline (Stage: Needs Contact). Partner-sourced leads land in the Partner Referral pipeline (Stage: Qualifying). Same webhook, different destination.

Once the contact + opportunity exist, the workflow triggers everything: internal notification (email + in-app) to the assigned rep with the lead's info + direct GHL link, branded welcome email + SMS to the lead within seconds, and enrollment into the source-specific nurture sequence (different follow-up cadence for ad leads vs referral leads vs cold leads).

The exact same webhook endpoint now accepts leads from anywhere — Facebook Ads via Zapier/Make, Google Ads lead forms, partner sites, third-party portals like Zillow/PropStream/BatchLeads, even manual CSV imports mapped through Make. One authentication pattern (sub-account token + location ID), one parser, one pipeline router — every new lead source is a same-day integration instead of a rebuild.

The client's world becomes: publish a page in AI Studio, plug in a new lead source, and leads flow into GHL tagged, welcomed, in the right pipeline, with the sales rep already notified — all before anyone touches a keyboard. That is the actual product I ship: not a website, but a reusable lead-ingestion nervous system built around their GHL sub-account.