How to connect GoHighLevel to any website: WordPress, Wix, Lovable (2026)

In my video I call it four ways, because I count forms, calendars and the chat widget separately, plus Zapier. They boil down to three routes. The one you pick decides your attribution and how the form looks, and it's where duplicate contacts come from.

Embed code is the default. You make the form, calendar or chat widget in HighLevel and paste a snippet into the site. You give the snippet to the client's developer, or if they built the site themselves they stick it wherever they want the form and replace their old one. The WordPress plugin is the same thing with a nicer install. The third route is keeping the site's own form and sending its data in, either with an Inbound Webhook, Zapier or Make, or HighLevel's External Tracking script.

Go to Sites > Forms, open the form and click the Integrate tab (it replaced the old Integrate button). Under Embed, pick the type: Standard sits inside the page, Popup opens as an overlay, Popover opens from a floating button, and Sidebar slides in from the side. Set the size and button, check the live preview, then Embed code > Copy code and paste it into the site.

Paste the whole snippet. It's an iframe plus a script (form_embed.js), and the script is what resizes the form, runs popups and passes the page's URL parameters and UTMs into the form. An iframe on its own will show the form, but those things stop working.

Then wire the follow-up: a workflow with the Form Submitted trigger, filtered to that form. The Connections section in the Integrate tab shows which workflows already use it. Every form, survey and calendar booking that comes through this way gets HighLevel's attribution on the contact, which the webhook route doesn't. The full workflow builder walkthrough is in GoHighLevel workflows.

Go to Sites > Chat Widget, click New and pick the type: All-In-One, SMS/Email, Live Chat, Facebook, Instagram, WhatsApp or Voice AI. Style it, then use Get Code and paste the snippet into the site's head or footer so it loads on every page. A lot of people don't know about this one, and it's the easiest lead source on the site.

Two things to set up before you call it done. If it's the SMS/Email type, the sub-account needs a phone number and a finished A2P registration, or the text replies don't send. And add a workflow with the Customer Replied trigger filtered to Reply Channel = Chat Widget, with an internal notification, so someone actually sees the message. HighLevel suggests putting {{message.body}} in the notification so the message is right there in the text.

Want it to answer on its own? Turn on Conversation AI inside the widget. How I train the bot so it doesn't sound like a bot is in Train Conversation AI. One limit: the widget's messaging is the same on every page, but you can make more than one widget per sub-account.

Go to Calendars > Calendar Settings, click the three dots on the calendar, choose Share, then the Embed Code tab, and copy it. Paste it into a custom code block on the page. The Share menu also gives you a plain booking link if you'd rather send people to it.

When someone books on the client's site, the appointment lands in HighLevel and the Customer Booked Appointment trigger fires. Filter it to the calendar you embedded and run your confirmations and reminders from there.

If the business runs Facebook lead ads, the same calendar link can go in the Instant Form's Book time button so people book straight from the thank you page. HighLevel's doc says to use the LeadConnector-domain link there, because branded-domain links may open in a browser instead.

This is the newer option, and super underrated. Go to Settings > External Tracking, copy the script and paste it before the closing body tag on every page of the external site. It then detects normal HTML forms on the page and sends each submission into HighLevel as a contact, with the UTMs, page URL and session.

It works with WordPress forms like Gravity Forms, WPForms and Contact Form 7, custom HTML forms and many no-code builders. The form needs a real <form> element, fields with name attributes and an email field. Password, payment and hidden fields are never captured.

Submissions show under Sites > Forms > Submissions > External Forms, and you get two workflow triggers: Page View and Form Submission, with filters for domain, page, form name and UTMs. As of late October 2026 there's also a Labs version with per-domain switches, your own field mapping, and a two-snippet setup for forms inside cross-domain iframes.

Each form field has a query key in its settings. Add those keys to the page URL and the field fills itself, for example yoursite.com/book?first_name=Sam&email=sam@example.com. On an external site this only works when the full embed snippet is on the page, because form_embed.js is what reads the page's URL and hands it to the form.

Where this pays off is follow-up texts and emails. Put a link like ?first_name={{contact.first_name}}&email={{contact.email}} in a workflow message and the person never retypes their details. Match the keys exactly, encode spaces as %20 and & as %26, and test the link before it goes out.

Two related settings. A Source element in the form records a contact source, and adding ?source=google-profile to the link overrides it, so one form can tell you which link people came from. Sticky Contact (Form Settings) fills in details for returning visitors on the same browser, but turn it off if staff fill in forms for customers on one device, or submissions update the wrong contact.

Same idea everywhere: site-wide code (chat widget, External Tracking) goes in the header or footer, and forms and calendars go in a code block on the page where you want them.

Say the client loves their Typeform or the form Lovable built, and they won't swap it. In Automation > Workflows, create a workflow, add the Inbound Webhook trigger and copy the URL it gives you. Point the form's webhook (or a Zapier, Make or n8n step) at that URL, send one test submission, and pick it as the mapping reference. Then add a Create Contact or Update Contact action and map name, email, phone and anything else. Then add the follow-up.

In my video I do it with Zapier: the trigger is a new Typeform entry, the action is LeadConnector (that's what HighLevel is called inside Zapier) > Create Contact, and you map first name, phone and so on. Whenever a lead submits on the client's non-HighLevel site, the contact shows up in the CRM like any other.

Inbound Webhook is a premium trigger. Each sub-account gets 100 free lifetime executions, then it's $0.01 per execution, or a Workflow Pro plan at $10, $25 or $50 a month for 10,000, 30,000 or 65,000 executions (HighLevel's help doc, read Nov 4, 2026). If the webhook URL ever leaks, delete the trigger and add a new one to get a new URL.

The catch is attribution. Contacts created through Zapier show the Third-Party source, and none of HighLevel's page tracking comes along. If you report on lead source, send the UTMs in the webhook payload and map them to fields, or use the External Tracking script instead.

Form embeds in Lovable and other React sites. Two things go wrong. Lovable often rebuilds your form as its own React form, which looks right and sends nothing. And a <script> tag inside a React component doesn't run, so the iframe shows without the script that sizes it and passes URL parameters. Fix: paste the full embed code into the Lovable chat, say it's a HighLevel embed that must be added exactly as given, and ask for form_embed.js to be loaded in index.html. If you'd rather keep Lovable's own form, have it post to your Inbound Webhook URL, or make it a real <form> with name attributes and install the External Tracking script. Always test on the published URL.

Safari and iPhone. People report iPhone users who can't open a survey and quizzes that misbehave outside Chrome. HighLevel's embeds are iframes from another domain, and Safari blocks cross-site tracking by default, which is where a lot of these start. Test every embed in Safari on an actual iPhone before handing it over. Use the Standard form type for anything long, never nest the embed inside another iframe (like a Wix HTML box), and if a survey still won't load, link the button to the hosted form page instead of embedding it. You can't ask customers to change their Safari settings.

Duplicate contacts from Wix forms. This usually means two routes feed the same form, for example Zapier from Wix Forms plus the tracking script, or the sub-account allows duplicates. Pick one route per form. Then go to Settings > Business Profile > Contact Deduplication Preferences, turn Allow Duplicate Contact off, and match on email first and phone second. Existing duplicates can be merged. If it's duplicate pipeline cards, check that Allow Multiple Opportunities per Contact (Settings > Objects > Opportunities) is off and that only one workflow creates the opportunity.

Chat widget not showing on WordPress: it's almost always the cache. Clear the caching plugin, the host's cache and do a hard refresh. Plugin says Disconnected: someone regenerated the API key, so sign in again.

In my video I said it straight: design-wise WordPress might be better than HighLevel, but forms, chat widgets, surveys and calendars are what make a website functional. If the client is happy with their site, there's no need to move them. Connect it and run the automations.

When the site is old, slow, or nobody has the login anymore, I'd rebuild it in AI Studio. You describe the site, it writes it, and forms, calendars and chat widgets connect to the CRM from the chat. No embed codes, no second platform. I show the build in youtube.com/watch?v=lE83w3EmBfA, and the full setup with costs is in AI Studio tutorial. HighLevel also hosts WordPress sites and has a migration guide if the client wants to stay on WordPress.

Don't sell "I'll connect your website to a CRM". Nobody wants that. Sell a website that books jobs: every form gets a text back in seconds, the chat answers after hours, and the booking calendar is on the page. That's one of the first things I'd offer a local business, because the owner gets it straight away and you can see the gap on their site before you ever call them: no booking, a contact form that goes to an inbox nobody checks, no chat.

Send one real inquiry through their current form and see how long the reply takes. Then show them the same thing on a demo site. You could build this for a local business and charge a setup fee plus a monthly fee you set, and the monthly part is the follow-up that keeps running. More on pitching it in Sell AI to local businesses.