LeadConnector

Your Webflow site ships fast, semantic pages. But form submissions land in a table and sit there until someone copies them into a sales tool. That handoff delay is where leads go cold.

LeadConnector closes the gap. A submission can create a contact, apply a tag, assign a pipeline stage, fire an immediate SMS, and enroll the lead in an email sequence, while booking calendars and other widgets embed directly on your pages.

How to integrate LeadConnector with Webflow

LeadConnector is a white-label all-in-one CRM and marketing automation platform within the GoHighLevel ecosystem. It handles contacts and SmartLists, pipelines and opportunities, phone and SMS messaging, email building, scheduling calendars, and workflow automation. Its workflows can capture leads into CRM records and send welcome emails without writing code.

Teams reach for this combination when a site needs to do more than collect submissions. A consultation form should qualify the lead and route it to a pipeline. A booking calendar should confirm the appointment and schedule an SMS reminder. LeadConnector supplies the CRM and automation layer while your site handles the design and hosting.

There's no LeadConnector app in the Webflow Marketplace, so every method here uses manual configuration. Embed codes and the External Tracking script capture form data and render LeadConnector widgets on your pages without automation platforms. When submissions need to move between systems, automation platforms can connect your form submissions to LeadConnector contacts, opportunities, and campaigns with no code. Custom API work between the two platforms gives you full control over CMS sync and event-driven pipeline routing, but requires server-side development.

Most implementations combine two or more of these methods depending on the complexity of the setup.

Add LeadConnector components with embeds and tracking

The most direct path uses the Code Embed element and Custom code in head and body tags to place LeadConnector scripts on your pages. This covers form tracking, embedded LeadConnector forms, booking calendars, chat widgets, and review widgets. You need a paid workspace plan (Core, Growth, Agency, or Freelancer) or an active Site plan to add custom code. All of these methods are copy-paste, so no coding is required.

Use a Code Embed element to insert a script at a specific spot in a page layout. Use Custom code in head and body tags to add scripts globally across every page or per page, with a 50,000-character limit each in the Head and Footer sections.

Track native Webflow forms with the External Tracking script

The External Tracking script is LeadConnector's closest thing to a native integration. It records page views and captures submissions from native forms automatically. It works only with forms rendered directly in the DOM as valid HTML, which native forms are.

To install the tracking script:

1. In LeadConnector, open your account settings and copy the External Tracking script.
2. Go to Site Settings > Custom Code and paste the script into the Footer section, before the closing </body> tag.
3. Publish the site. The script does not run in preview mode.
4. Confirm your form fields use standard HTML name attributes like email, phone, first_name, and last_name.

The script scans for supported forms and maps submissions to LeadConnector contacts. Forms inside iframes, popups, or JavaScript widgets won't be tracked, so this approach and LeadConnector's own embedded forms are mutually exclusive.

Embed LeadConnector forms, calendars, and widgets

LeadConnector generates static embed codes for its forms, calendars, chat widgets, and review widgets. Paste these into a Code Embed element for page-specific placement or into site-wide custom code for components that load everywhere. This route enables conditional logic, multi-step forms, and custom fields that native forms can't produce.

To embed a LeadConnector form:

1. In LeadConnector, open the form and go to the Integrate tab in the top right corner.
2. Select the layout: Inline, Popup, or Sticky Sidebar, then click Copy Embed Code.
3. Drop a Code Embed element where you want the form and paste the code.

The same pattern covers other assets:

• Calendars live under Calendars > Calendar Settings > three dots icon > Share > Embed Code tab > Copy. GoHighLevel-hosted funnel and website pages generally can't be embedded in external iframes because of security headers; calendar embeds are an exception.
• Live chat widgets use Style tab > Widget Placement > Embedded/Inline > Get Code for inline placement, or paste the floating snippet into site-wide Footer code. Review widgets come from Reputation > Code icon > Copy Code.

Embed codes are static, so any form or widget change requires regenerating the code and replacing it on your page. LeadConnector forms load inside an iframe, so your CSS can change only the iframe wrapper's spacing and width.

Connect with Zapier, n8n, or viaSocket

When you want LeadConnector-branded forms but still need submissions in your CRM, automation platforms bridge the gap. Zapier connects the two directly, as do n8n and viaSocket.

With these platforms, a form submission can:

• Form submission → create or update a LeadConnector contact in Zapier.
• Form submission → create or update a LeadConnector opportunity in a pipeline.
• Form submission → add a lead to a LeadConnector campaign in Zapier.
• The Webflow node paired with the HighLevel node in n8n, which supports creating, updating, deleting, and getting contacts, opportunities, and tasks.
• Real-time or scheduled sync of submissions to contacts, tasks, or opportunities in viaSocket.

Reach for these platforms when forms render inside iframes or widgets and the tracking script can't handle the data sync.

Build custom server-side workflows

For full control over CMS sync and event-driven pipeline routing, connect the two platforms through custom server-side development. You'll need a server-side runtime because the front end supports only HTML, CSS, and JavaScript. Run backend logic on an external serverless platform like AWS Lambda or Pipedream. A middleware endpoint also keeps your API keys server-side rather than exposing them in client code.

For custom builds, connect through:

• The LeadConnector API at https://services.leadconnectorhq.com/ handles contacts and opportunities using OAuth 2.0 or Private Integration Tokens. Note that API V1 reached end-of-support on December 31, 2025, so build on v2.0.
• The Webflow Data API handles CMS collections and form submissions, while webhooks trigger real-time events between systems.

Use webhooks instead of aggressive polling to avoid hitting rate limits.

Send Webflow form submissions to LeadConnector contacts

The cleanest programmatic pattern registers a webhook that fires on every submission, then posts the payload to LeadConnector. This creates or updates a contact the moment a visitor submits a form.

To set this up:

1. Register the trigger with POST https://api.webflow.com/v2/sites/{site_id}/webhooks. Use a body of { "triggerType": "form_submission", "url": "<your-receiver-endpoint>" } and the forms:read scope.
2. Receive the form_submission payload, which includes the form name, siteId, formId, and a data object with the submitted fields.
3. Forward the data to LeadConnector. For a no-code path, add an Inbound Webhook trigger to a LeadConnector workflow and POST the JSON to its generated URL. For a programmatic path, call POST /zapier/contact/add_update with a Bearer token.

Either way, the payload must include email or phone for LeadConnector to create or map the contact.

Log Webflow leads as pipeline opportunities

Once a contact exists, log the lead into a sales pipeline stage. This suits consultation forms and e-commerce orders where each submission should become a tracked opportunity.

To create the opportunity:

1. After the contact call succeeds, call POST /zapier/add_update_opportunity with a Bearer token in the Authorization header.
2. For e-commerce orders, register the ecomm_new_order webhook with the ecommerce:read scope and map customerInfo fields into the opportunity.
3. For CMS-driven flows, register collection_item_created or collection_item_changed with the cms:read scope and route changes into LeadConnector.

For the reverse direction, use LeadConnector's Custom Webhook workflow action to POST to endpoints like POST /v2/collections/{collection_id}/items. This keeps CMS items in sync with CRM records.

What can you build with the LeadConnector Webflow integration?

Pair LeadConnector with your site and you can turn form submissions into automated follow-up without manually copying leads between tools.

• Lead capture with CRM routing: A contact form fires into LeadConnector, which creates a contact, applies a "New Lead" tag, assigns a pipeline stage, and sends an immediate SMS. A consultation page with budget and timeline fields routes qualified leads to a pipeline while nurturing the rest.
• Appointment booking pages: Embed a LeadConnector calendar on a page so visitors book directly. On booking, LeadConnector creates the contact, sends a confirmation email, delivers an SMS reminder 24 hours before, and creates a task for the assigned team member. Coaches use this for discovery call scheduling.
• Real estate lead routing: A property listing site captures inquiries and routes them to agents by location and price range, triggers SMS follow-up, and enables appointment booking, all through LeadConnector pipelines and calendars.
• CMS-powered registration pages: Build employer-specific or event pages in the CMS and connect each form to LeadConnector for webinar registration and consultation booking. Exact Medicare runs this pattern for Medicare consultation and resource access.

If you need more control over two-way CMS sync or real-time e-commerce events, the API integration path covers those cases with full flexibility.