Close integration

Every form fill from your ads becomes a Close lead with its contact attached and the phone number ready to dial, the moment the form is sent. No Zap, no CSV.

  • Webhook
  • Landing pages, Quiz funnels, Workflows (beta, by HTTP Request)

Why connect it

Why Close and LanderLab

  • From form to dialer in seconds

    The lead and its contact exist in Close as soon as the form is sent. A Smart View of today's leads becomes a call list that fills itself.

  • Lead and contact in one request

    Close's API creates the lead, the contact inside it, the email, the phone and your custom fields together, so nothing arrives half-built.

  • Campaign and variant on every lead

    UTMs, click IDs, the landing page and the A/B variant go into Close custom fields, ready for Smart Views and reports by ad set.

  • Quiz answers reps can see before dialing

    Home value, coverage, team size: each answer lands in a custom field or the lead description, so the first call starts with context.

  • No middleware bill

    The page talks to Close's API directly. No Zapier plan, no task limits, no third login to check when something looks off.

Close on your landing pages

Close is built for teams that win on the phone, and phone teams win on speed. A paid lead that reaches the dialer an hour late has already talked to someone else. Sending your LanderLab leads to Close puts each one in front of a rep as it's submitted: a lead, its contact, the contact's email and phone, and your campaign fields, created in one go.

It's a fit for insurance agencies working Meta quote leads, solar and home improvement setters booking appointments, and B2B inside sales teams following up on demo requests. LanderLab's webhook posts each lead to Close's API, so there's no connector or Zap to pay for, and the rep can call from Close straight away with the campaign and page variant already on the record.

A Close lead with its contact, created on submit

In Close a lead is the household or the company, and contacts sit inside it. LanderLab sends both in one request to Close's API: a lead name, then the person with their email and phone, plus any custom fields you use. Leave the status out and the lead starts in your default status; name one, and page leads start where you want them.

Close creates a new lead for every request; its API doesn't merge on email. Close's duplicate finder can merge a repeat, and the second submit tells the rep the person is still shopping.

Ready to call from Close the moment it lands

A paid lead is worth most in the first minutes. Build a Smart View in Close for leads created today with your campaign field set, and your reps call down that list as leads arrive, with the dialer in the same window. The page did its job when the form was sent; the call happens while the person still remembers why they filled it in.

Campaign, page and variant in Close custom fields

Hidden fields on the page capture utm_campaign and the click ID from the ad's URL, and LanderLab adds the page URL and the variant the visitor saw. In Close they become custom fields, so a Smart View or report split by campaign shows which ad sets produced leads that answered, booked and bought.

That's what your bids should follow. An ad set with a cheap cost per lead whose leads never pick up shows up in Close long before the monthly report.

Send Close only the leads worth a dial

If reps should only call homeowners, or only finished quizzes, put the rule in LanderLab Workflows (beta): a Filter or If node in front of an HTTP Request node that makes the same call to Close. Everything else stays in LanderLab's Leads tab, and the Runs view shows why each lead went where it did.

Use cases

Ways to use Close on paid traffic

  • 01

    Insurance quotes worked by phone

    A home or auto insurance page on Meta sends each quote request to Close. Agents call from a Smart View of today's leads, and the variant field shows which page version brought the policies that bound.

  • 02

    Appointment setting for solar and home improvement

    A quiz on roof type, power bill and ownership creates a lead with the answers in custom fields. Setters skip renters, call homeowners first and book the visit on the first dial.

  • 03

    Demo requests for a B2B inside sales team

    A demo page on Google Search sends the company as the lead and the requester as its contact. The SDR calls and emails from Close, and the campaign field ties each deal to the keyword that bought it.

FAQ

Close integration FAQ

Anything not here, ask us.

Close and LanderLab

When is Close worth connecting to my landing pages?

When your reps sell by phone from Close: leads reach the dialer seconds after the submit, with the answers and the campaign on them.

Does LanderLab integrate with Close?

Yes, through the page's Webhook integration: it calls Close's API on every submit, which creates the lead, its contact and your custom fields in one request.

Do I need Zapier to send leads to Close?

No. The webhook posts straight to Close's API, so there's no Zap to pay for or keep running.

Will Close see my UTMs and the A/B variant?

Yes. Hidden fields capture the UTMs and click ID from the URL, and LanderLab adds the variant; each goes into a Close custom field.

Can I send quiz answers to Close?

Yes. Each answer can go to its own custom field, or into the lead's description for the rep to read.

Other integrations

Plug in the rest of your stack.

Connect Close and launch your next page.

Build the page, switch Close on and send your ads to it. Free to start, no card.

From one prompt to qualified leads

Watch one prompt become a live solar quote funnel, every lead routed to your buyer, and the leaks flagged before they eat your budget.

0:00
0:59