How to Capture Website Leads Automatically in a CRM

There are three practical routes: point people at a hosted form, post your own form to a REST API endpoint, or have another tool send a webhook. All three remove the retyping step, which is where most lost leads actually go.

Published 2 November 2026 · Solvix CRM

Manual entry is the weak link in lead capture. An enquiry arrives by email, somebody means to copy it into the system, and it sits in an inbox instead. Automatic capture fixes it by writing the lead at the moment it is submitted.

Which route you pick depends on how much control you have over the page the enquiry comes from.

Route 1: a hosted form

The simplest option. The CRM gives you a form on its own link; you share that link or embed it in a page, and submissions arrive as leads. There is nothing to build and nothing to deploy.

This is usually the right starting point if you sell through WhatsApp, Instagram bio links or a Google Business profile rather than a website, because a link is all those places accept anyway.

Two things to check on any hosted form before you rely on it:

• Spam protection. An open form on a public URL will be found by bots. A hidden honeypot field and a rate limit per IP deal with nearly all of it without making real people solve puzzles.
• Whether it can be embedded. If you want it inside your own page in an iframe rather than as a separate link, the form has to allow framing.

Route 2: your own form, posting to a REST API

If you already have a website form you like, keep it and change where it posts. Your form stays on your domain, in your design; the CRM just receives the data.

In Solvix Mini CRM the endpoint is:

POST https://solvixcrm.com/minicrm/app/api/capture/lead
Content-Type: application/json
Authorization: Bearer YOUR_CAPTURE_TOKEN

{
  "name":    "Ravi Kumar",
  "phone":   "9876543210",
  "email":   "ravi@example.com",
  "company": "Kumar Interiors",
  "source":  "website",
  "notes":   "Asked for a quote on 3 rooms"
}

name and phone are required; the rest are optional. The token can travel as a Bearer credential, as an X-Capture-Token header, or as a token field in the body — whichever your stack finds easiest.

Do not put the token in client-side JavaScript

This is the mistake worth calling out. A capture token in front-end code is visible to anyone who opens the page source, and it can then be used to write leads into your account from anywhere. Post from your server: the browser submits to your own backend, and your backend calls the CRM with the token. If you have no backend at all, use the hosted form instead — that is exactly the case it exists for.

Handle the failure case

A capture endpoint can refuse a submission: a bad token, a missing name, a rate limit, a body too large. Decide what the visitor sees when that happens. The worst outcome is a form that silently appears to succeed while nothing was saved. Show an error and keep the enquiry somewhere — an email to yourself is a fine fallback.

Route 3: a webhook from another tool

If something else is already collecting the enquiry — a form builder, a landing page tool, an automation platform — it can usually send a webhook. You paste a URL into that tool and it posts each new submission for you.

POST https://solvixcrm.com/minicrm/app/api/capture/webhook/YOUR_CAPTURE_TOKEN
Content-Type: application/json

{ "name": "Ravi Kumar", "phone": "9876543210", "source": "website" }

The token sits in the path here, because most webhook senders let you set a URL and nothing else. The body is the same as the API route.

Be realistic about Facebook and Instagram lead ads

This is where product pages tend to overpromise, so it is worth being plain. A webhook endpoint is not the same thing as a one-click Facebook or Google integration. To get Meta lead ad submissions into a CRM you need something on the Meta side — an app with the right permissions, or an automation platform sitting in the middle — and that is setup work on the source, not a toggle in the CRM.

Four things to do once capture is live

1. Send a real test submission and confirm the lead appears, with every field in the right place. Then send a deliberately broken one and see what the visitor gets.
2. Set the source on every route, so you can tell later which channel paid for itself.
3. Decide the first follow-up. Automatic capture puts the lead in the system; it does not contact anyone. Give new leads a next action the same day.
4. Keep the token rotatable. If it ever leaks, regenerating it should be a one-minute job, and you should know where the old one is used.

The point of all this

Automatic capture is not really a convenience feature. It removes the step where a human has to remember to move an enquiry from one place to another — and that step is where lost leads come from. Pick whichever of the three routes matches what you already have, get it working end to end, then put a follow-up date on everything it brings in.

Related