Connecting your landing page form to a CRM or email tool: Zapier, Make, webhooks

LanderKit templates ship with ready-to-use forms — email field, button, confirmation message — but deliberately not wired to anything: it's up to you to connect the submission to your CRM, your email tool, or your spreadsheet. This step, often pushed to "later," is what actually turns a static page into a lead machine. This guide walks through the three ways to do it — hosted third-party service, no-code automation with Zapier or Make, native webhook — with the criteria to choose without losing a week or hiring a developer.

The form captures the lead — it still has to land somewhere

An HTML form that just shows "Thank you!" in the browser is useless on its own: with no destination, the response disappears the moment the visitor closes the tab. For an email, a phone number, or a qualification answer to become usable, the submission has to be sent somewhere — an inbox, a CRM (HubSpot, Pipedrive, Notion), an email tool (Brevo, Mailchimp, ActiveCampaign) or, more simply, a spreadsheet shared with the sales team. Our complete guide to the form covers the fields, the order and the microcopy; this one covers the next step, which plays out on the technical side rather than the design side.

Why automation changes everything: callback speed

The wiring method isn't just a matter of technical convenience — it has a direct effect on how many leads turn into customers. The study by James Oldroyd (MIT), Kristina McElheran and David Elkington, published in Harvard Business Review in 2011 (available on Google Scholar), audited more than 100,000 web leads sent to 2,241 US companies: those that recontacted a prospect within the hour were nearly 7 times more likely to qualify them than those that waited even one more hour — and more than 60 times more likely than those that took 24 hours. A form wired directly to a CRM with an instant notification closes that window; a form whose responses pile up once a day in an untriaged inbox leaves it wide open. Our article on the ideal callback delay for a lead details what to aim for once the notification lands.

The hidden cost of manual copy-pasting

Without automation, someone has to open each notification email, re-read the fields and retype them into the CRM — a task that looks trivial in isolation but fragments a workday and accumulates errors. Cognitive psychology research on task-switching costs backs this up: the study by Rubinstein, Meyer and Evans, published in 2001 in the Journal of Experimental Psychology: Human Perception and Performance (available on Google Scholar), shows that switching from one task to another imposes a measurable reaction-time cost at every switch, one that grows with the complexity of the rule being applied. Retyping a lead means stopping what you were doing, re-reading, retranscribing, then resuming — do that ten times a day and it weighs on the rest of the work, not counting the risk of a typo in an email or phone number that makes the lead simply unreachable.

Three ways to wire a form to an external tool

• A hosted third-party service (Formspree, Getform, Web3Forms…): point the form's action attribute at their endpoint, which relays to an email or a spreadsheet. Set up in a few minutes, free or nearly so up to a certain volume, but limited for what comes next — no conditional logic, no splitting between several tools.
• No-code automation (Zapier, Make): the form sends its data to a webhook provided by the platform, which then redistributes it to the CRM, the email tool and a Slack or WhatsApp notification, in a few clicks and without writing code.
• A native webhook coded into an API route on the site: the submission goes straight to the CRM's or email tool's API, with no middleman or extra subscription — the most robust and cheapest method to run, reserved for those who can code a little or have a Next.js route edited for them.

Zapier or Make: how to choose between the two

Both tools do the same thing in principle — receive a form submission and push it to other services — but with different philosophies. Zapier favours simplicity: a linear "trigger → actions" interface, a very wide catalogue of integrations, a price that climbs fast with the number of tasks run. Make (formerly Integromat) offers a visual flow-based editor, with conditional branches, loops and finer data transformations for the same budget — at the cost of a slightly longer learning curve. For a simple "form → CRM → welcome email" relationship, Zapier is more than enough and takes ten minutes to set up. As soon as the logic gets more complex — routing leads by city, creating a task in the project tool on top of the CRM, deduplicating before sending — Make absorbs that complexity without multiplying paid steps.

The native webhook, for those who'd rather skip another subscription

LanderKit templates are self-contained Next.js projects: adding an API route that receives the form submission and forwards it to the chosen CRM's or email tool's API only takes one more file in the app/api/ folder. That route receives the fields via POST, validates them server-side, then relays them with the CRM's secret key — never exposed to the browser, unlike a call made directly from the form component. It's the cheapest method over time (no automation subscription) and the fastest at runtime (a single network hop instead of two or three), at the cost of a bit of code to write and maintain once. Our guide to deploying a Next.js landing page on Vercel covers shipping this kind of route.

What to send with each lead, not just the email address

• The session's UTM parameters (source, medium, campaign) to know which ad generated the lead — see our guide to UTM tracking.
• The originating page or offer, useful as soon as several landing pages or templates run in parallel.
• The exact date and time of the submission, needed to measure the time to first contact.
• Proof of the consent given (newsletter, sales contact) with its timestamp, required under GDPR in case of an audit — see our article on the GDPR-compliant form.
• The single/double opt-in status if the lead joins an email list, a point covered in our comparison of double opt-in versus single opt-in.

The mistakes that quietly lose leads

• No safety net if it fails: if the webhook or the automation goes down, the form should at minimum store the submission server-side or send a fallback email — a CRM outage should never make a lead vanish without a trace.
• No end-to-end test before launching a paid campaign: submitting the form yourself once and checking the lead actually reaches the CRM avoids discovering the outage after spending the ad budget.
• An API key exposed client-side: the CRM's or email tool's secret key must never appear in the code shipped to the browser — it should stay in the server route or in the automation's configuration.
• No deduplication: a visitor who submits twice out of impatience shouldn't create two records or trigger two welcome sequences.
• A notification that drowns: one more email in an already-full inbox gets handled a day late; a Slack or SMS notification, or an automatic CRM task, gets seen within minutes.

Checklist before calling the wiring done

1. A method chosen (hosted service, Zapier, Make, or native webhook) based on budget and available technical skill.
2. The useful data sent with each lead: UTM, originating page, timestamp, proof of consent.
3. An API key or secret never exposed client-side.
4. An end-to-end test run before any paid campaign.
5. A safety net if the automation or the CRM goes down.
6. An instant notification for the sales team, not just a daily email digest.
7. A clear follow-through after submission: thank-you page and, where relevant, a welcome email sequence.

Every LanderKit template ships with a form already designed for its use case — simple capture on the newsletter template, qualified callback on the training template, two-step qualification on the real-estate valuation template — with a comment in the code marking exactly where to plug in your tool. All that's left is to pick the method that fits your budget and follow it with our complete CRO checklist before publishing a campaign.