Skip to content

Capturing leads automatically

Web forms, webhooks, Meta and Google Lead Ads, and the on-site pixel.

3 min readUpdated 30 July 2026
Lead capture
Six intake paths, one lead record
Meta Lead Ads
Campaign, adset, ad and form attached to the lead
Google Ads
GCLID captured at the form for offline conversions
WhatsApp
An inbound message becomes a lead and a thread
Website forms
Public capture endpoint, no login, spam-guarded
IVR & calls
A call to a virtual number creates or matches a lead
CSV & REST API
Bulk migration and anything else you already run
Whichever path a lead arrives on, deduplication runs before assignment — so two agents never call the same person.

Manual entry does not scale and import is for history. This is how leads arrive on their own.

Capture sources

Everything that creates leads automatically is configured in Settings → Integrations → Capture sources.

Each source gets its own credential and its own settings, which means you can tell exactly where a lead came from and switch one channel off without touching the others.

Web forms and webhooks

Create a capture source of type Webhook. You get a URL containing a token:

https://api.nexuscrm.com/api/capture/YOUR_TOKEN_HERE

POST a JSON body to it:

json
{
  "name": "Aarav Patel",
  "phone": "9812300045",
  "email": "aarav@example.com",
  "city": "Mumbai",
  "message": "Interested in the annual plan"
}

The response tells you whether a lead was created or matched an existing one.

Per-source settings worth knowing:

  • Default stage — where these leads land
  • Assign to — override distribution and send this source to one person
  • Require signature — HMAC verification, for sources you control
  • Allowed IPs — restrict which servers may post
Note
The token is the credential. Anyone who has it can create leads in your workspace. Treat it like a password, and rotate it if a form using it is ever publicly exposed in a way you did not intend.

Meta Lead Ads

Go to Marketing → Manage Facebook and connect your account.

Once connected, pick which pages and which lead forms to subscribe to. Leads arrive within seconds of submission, carrying their campaign, ad set and ad — which is what makes cost-per-conversion reporting possible later.

You can also send conversions *back* to Meta so its optimisation learns from closed deals rather than form fills. See Marketing → Conversions API.

Marketing → Google Conversions connects your Google Ads account. This does two things:

  1. Ingests spend, so cost per lead and cost per conversion are real numbers rather than estimates.
  2. Uploads offline conversions, so Google optimises toward leads that actually closed.

The on-site pixel

For your own marketing site. Settings → Integrations → Pixel gives you a script tag:

html
<script src="https://api.nexuscrm.com/pixel.js" data-site-key="YOUR_SITE_KEY"></script>

It records page views and form submissions on your site and attributes them to the lead once that person converts. First-party, no third-party cookies.

Inbound calls

If you use a supported telephony provider, calls to your tracked numbers create leads automatically, with the recording attached. See Telecalling.

Checking that capture is working

Settings → Integrations → Capture sources shows, per source, when it last received something and how many failures it has had recently.

A source that has received nothing for a day it normally would is the single most common cause of "our leads dropped" — and the anomaly detector will usually flag it before anyone notices manually.

Something unclear or missing? Tell us and we will fix the page — send us a note.

Capturing leads automatically — Documentation — atomcrm.ai