A real webhook, clearly described
JSON over HTTPS, posted when the lead is submitted. No hidden connectors to maintain.
Feature · HighLevel & CRM sync
Paste a webhook URL once and every lead is posted to it the moment the visitor submits, carrying the contact, the full calculation and the campaign it came from. It is a plain HTTPS webhook, so it reaches HighLevel workflows, Zapier, Make or your own endpoint.
InsuranceQuoteWidget sends each new lead as a JSON POST to the webhook URL you provide. In HighLevel, that URL comes from a workflow's inbound webhook trigger, so the lead can create a contact, set custom fields from the calculator results, tag it and start a follow-up sequence. The same payload works with Zapier, Make or any HTTPS endpoint.
How it works, step by step
In HighLevel, add a workflow with an inbound webhook trigger and copy its URL. In Zapier or Make, start a catch-hook scenario instead.
Add it as your agency-wide webhook, or on a single calculator when that calculator's leads need their own route.
Submit the calculator yourself so the receiving workflow sees a real payload and can map its fields.
Point contact name, email, phone, calculator results and utm_* values at the contact fields and custom fields you use.
Tag by calculator, assign an owner, open an opportunity and start the sequence your consent language allows.
What you get
JSON over HTTPS, posted when the lead is submitted. No hidden connectors to maintain.
Route by calculator, with an agency-wide fallback for the rest.
Inputs and results arrive with the contact, ready for custom fields.
utm_*, gclid, fbclid and msclkid map straight to CRM fields.
For CRMs without an inbound webhook, relay the same payload through either.
It travels by webhook. When a visitor submits the lead form, InsuranceQuoteWidget posts a JSON payload to the URL you saved. A HighLevel workflow with an inbound webhook trigger receives it, and your workflow actions decide what happens next: create or update the contact, write custom fields, add tags, create an opportunity and notify the producer.
We describe it honestly: this is a one-way push of new leads, not a two-way sync. Notes and statuses you change in HighLevel stay in HighLevel; the built-in agency contacts list keeps its own copy of every lead.
Because the payload is ordinary JSON over HTTPS, the same setup works for any CRM that accepts webhooks directly, or through Zapier or Make when it does not.
The payload names the event and the calculator, says whether this is a new contact, and includes the contact details, the submission with every input and result, and the submission time. Attribution arrives both as a nested object and as flat fields, so mapping utm_source or gclid into a CRM field needs no extra parsing.
Yes. Every calculator can have its own webhook; if it has none, its leads go to the agency-wide webhook. That lets an agency send Medicare-age and annuity leads to the retirement team's pipeline, life and disability leads to protection producers, and keep one catch-all route for everything else.
Per-calculator routing is also how agencies with separate HighLevel sub-accounts per producer or per office keep leads apart without building filters downstream.
If you want one route and a smarter workflow instead, the calculator field in the payload is enough to branch inside HighLevel.
Webhooks are included on the Agency and Enterprise plans; the free Producer plan has none. The insurance calculators themselves are on every plan. Whatever you automate downstream, make sure calls and texts match the consent the visitor gave, since TCPA rules apply to autodialed calls and marketing texts.
A sensible first workflow sends an internal notification and a single email acknowledgement, leaving texts and dialer campaigns until you have confirmed the consent wording with your compliance contact. Nothing on this page is legal advice. See integrations for setup notes.
All features
Every lead arrives with the inputs and results the visitor entered, so the first call starts at question five.
One div and one script puts a calculator on any agency website or HighLevel funnel, isolated from your site's styles.
Bundle several calculators into one embed: a floating launcher, tabs, popup buttons or a card grid.
Themes, colour palettes, custom fonts, light and dark modes and custom CSS make every calculator look like your agency.
FAQ
Answers first, details after.
No, and we don't call it one. It is a webhook you paste into InsuranceQuoteWidget, pointing at an inbound webhook trigger in a HighLevel workflow. That is simple to set up, and it gives you full control over what the workflow does with each lead.
Only a workflow that starts with an inbound webhook trigger, which gives you the URL to paste. After a test submission, you map the incoming fields to contact fields and custom fields inside the workflow.
Yes. The submission object carries each input and result, so you can map, for example, recommended coverage or funding gap into custom fields and use them in smart lists, pipeline values or follow-up messages.
No. The webhook pushes new leads outward only. Notes and statuses you set in HighLevel stay there, and the built-in contacts list keeps its own record of each lead.
Any CRM that accepts an HTTPS webhook can take the payload directly. If yours doesn't, Zapier or Make can catch the webhook and create the record for you.
Yes. Give each calculator or embed its own webhook URL, pointing at the producer's workflow or sub-account. Calculators without their own webhook use the agency-wide one.
Webhooks come with the Agency and Enterprise plans, from $150 a month. The insurance calculators themselves are included on every plan, the free Producer plan too; see pricing for every option.
The lead is still stored in your built-in contacts list and you still receive the email alert, so it is not lost. Check your workflow's history after any outage and add the missing contacts by hand.
Technically yes, inside your HighLevel workflow. Make sure your lead form's consent language covers texting, especially marketing texts or automated messages, and check the plan with your compliance contact. This is not legal advice.
InsuranceQuoteWidget
/ Press / to search
Theme
Colour palette
Text size
Saved on this device