Website Lead Capture - Auto Detailing CRM

If you don’t need a full booking flow and just want website form submissions to land in the CRM as leads, use the website lead-capture integration. It’s the simplest way to connect an existing site (WordPress, Wix, Squarespace, or hand-written HTML) to Auto Detailing CRM.

Everything on this page is generated under Settings → Website Integration → Website Leads → Website Forms. Copy the snippet from there — this page explains what it does and how to customize it.

How it works

The Website Forms workspace gives you two things:

Your lead token — an opaque token that identifies your workspace.
An embed snippet — a small <script> that POSTs your form fields to the lead-capture endpoint when a button is clicked.

A submitted lead appears immediately in your Leads tab with the source set to Website.

The lead token ships in the installed browser code and only allows public lead creation for your workspace. Do not reuse it outside this integration. Regenerating it from Website Forms breaks every embed that still uses the old endpoint, so update your site afterward.

The embed snippet

The snippet wires a button on your page to the lead endpoint. It reads five fields by element ID — crm-name, crm-phone, crm-email, crm-service, and crm-message — and fires on a button with the ID crm-lead-btn. Fields you leave out of your form are sent empty.

<!-- Your form -->
<input id="crm-name" placeholder="Name" />
<input id="crm-phone" placeholder="Phone" />
<input id="crm-email" placeholder="Email" />
<input id="crm-service" placeholder="Service you need" />
<textarea id="crm-message" placeholder="Anything else?"></textarea>
<button id="crm-lead-btn">Request a quote</button>

This is the snippet itself. Website Forms gives you the same thing with your Endpoint URL already filled in and a one-click Copy code action:

<script>
(function() {
  var btn = document.getElementById('crm-lead-btn');
  if (!btn) return;
  function value(id) {
    var field = document.getElementById(id);
    return field ? field.value || '' : '';
  }
  btn.addEventListener('click', function() {
    var payload = {
      name: value('crm-name'),
      phone: value('crm-phone'),
      email: value('crm-email'),
      service: value('crm-service'),
      message: value('crm-message'),
      source: 'website'
    };
    fetch('YOUR_ENDPOINT_URL', {
      method: 'POST',
      headers: { 'Content-Type': 'application/json' },
      body: JSON.stringify(payload)
    }).then(function(response) {
      if (!response.ok) {
        return response.text().then(function(body) {
          console.error('CRM lead error', response.status, body);
        });
      }
      console.log('CRM lead submitted');
    }).catch(function(error) {
      console.error('CRM lead error', error);
    });
  });
})();
</script>

The snippet reports failures to the browser console rather than to the visitor — if leads aren’t arriving, open the console on your own site and look for CRM lead error.

Don’t assemble the URL by hand. Open Settings → Website Integration → Website Leads → Website Forms, copy Endpoint URL, and paste it in place of YOUR_ENDPOINT_URL.

The snippet doesn’t show the visitor a confirmation or clear the form. If you want either, add it in your own .then() — the fetch is left deliberately plain so it doesn’t fight your site’s styling.

WordPress with Contact Form 7

Contact Form 7 needs its own snippet because it submits over AJAX rather than a normal button click. Website Forms provides it — paste it into WordPress once and it listens to every Contact Form 7 form on the site.

This snippet covers Contact Form 7 only. Other form plugins and plain HTML forms need the standard embed snippet above. It also guards against being installed twice, so a duplicate paste won’t send every lead twice.

You probably don’t need to rename your fields

The snippet recognises the field names people actually use in Contact Form 7, so an existing form usually works untouched:

Lead field	Recognised names
name	`name`, `your-name`, `full-name`, `fullname`, `customer-name`, `client-name` — or `first-name` and `last-name`, which are joined
phone	`phone`, `your-phone`, `tel`, `telephone`, `mobile`, `mobile-phone`
email	`email`, `your-email`, `e-mail`, `mail`
vehicle	`vehicle`, `vehicle-type`, `car`, `car-type`, `auto`, `vehicle-size`
service	`service`, `your-service`, `subject`, `your-subject`, `request`, `type`
message	`message`, `your-message`, `comment`, `comments`, `inquiry`, `question`, `details`, `description`, `your-comment`

Matching ignores case, dashes, and underscores — Your_Name and your-name are the same field.

Everything else still reaches you

A field the snippet doesn’t recognise isn’t dropped. It’s appended to the lead’s message under a Fields: heading, with the field name tidied into a readable label. So a custom “Preferred contact time” question arrives in the lead even though there’s no column for it. Skipped entirely: submit buttons, consent and acceptance checkboxes, quiz fields, CAPTCHA tokens (hCaptcha, reCAPTCHA), and Contact Form 7’s own internal fields.

Which submissions are forwarded

Contact Form 7 fires its submit event on every attempt, including the ones it rejects itself. The snippet filters on that outcome:

CF7 status	Forwarded?	Why
Accepted	Yes	The normal case
`mail_failed`	Yes	The submission was valid and only the site’s mail server failed — exactly when capturing the lead matters most
`validation_failed`	No	The visitor mistyped something and will retry
`spam`	No	Already caught by the site’s own filter (Akismet, reCAPTCHA)
`aborted`	No	The submission never completed

Without that filter, a visitor who mistypes a field would create a junk lead on every retry, and spam your site already blocked would still reach the CRM.

Don’t replace the snippet with a plain wpcf7submit listener. A naive listener forwards rejected and spam submissions too.

Leads from this snippet arrive with source set to wordpress-contact-form, so you can tell them apart from the standard embed, which uses website. If a submission carries no usable values at all, the snippet skips it and logs a warning to the browser console instead of creating an empty lead.

WooCommerce orders

Selling jobs through a WooCommerce store is a separate integration with its own delivery URL, its own secret, and HMAC signature verification. It doesn’t use the lead token.

WooCommerce webhooks

Set up the webhook, verify signatures, and see what arrives in the lead.

Posting directly

If you’d rather call the endpoint yourself instead of using the snippet, POST a JSON body to the Endpoint URL copied from Settings → Website Integration → Website Leads → Website Forms. The token is already baked into that URL as the ?token= query parameter, so the simplest call needs no extra headers. The endpoint accepts the token two ways:

Where	How	Notes
Query	`?token=YOUR_TOKEN`	What the copied Endpoint URL uses — the simplest call needs no extra headers.
Header	`x-lead-token: YOUR_TOKEN`	Use this if you send a bare endpoint URL.

A request with no token in either place returns 401 with { "success": false, "error": "Missing lead token" }. A token that doesn’t resolve to a workspace returns 401 with "Invalid lead token".

// YOUR_ENDPOINT_URL = the Endpoint URL from Website Leads → Website Forms
await fetch('YOUR_ENDPOINT_URL', {
  method: 'POST',
  headers: { 'Content-Type': 'application/json' },
  body: JSON.stringify({
    name: 'Jane Doe',
    phone: '+1 512 555 0100',
    email: 'jane@example.com',
    vehicle: '2023 Toyota RAV4',
    service: 'Full Interior Detail',
    message: 'Prefer a morning appointment',
  }),
});

Fields

Field	Required	Notes
`name`	Recommended	Customer name (`customer_name` is also accepted).
`phone`	Recommended	Customer phone.
`email`	Recommended	Customer email.
`vehicle`	Optional	Free-text vehicle description.
`service`	Optional	Service the customer is interested in.
`message`	Optional	Free-text note (`comment` is also accepted).
`source`	Optional	Override the displayed lead source.
`utm_source`, `utm_medium`, `utm_campaign`, `utm_content`, `utm_term`	Optional	Marketing attribution, stored on the lead.
`gclid`, `fbclid`, `external_ref`	Optional	Ad-click and partner reference IDs.

Response

A successful submission returns 200 with:

{ "success": true, "lead_id": 1326 }

Failures return { "success": false, "error": "..." }, where error is a human-readable message rather than a code:

Status	`error`	Meaning
`401`	`Missing lead token`	No token in the query string or the `x-lead-token` header
`401`	`Invalid lead token`	The token doesn’t resolve to a workspace
`413`	`Payload too large`	The request body exceeds the size limit
`429`	`Too many lead submissions. Try again later.`	Rate limited

Booking API vs. lead capture

	Website lead capture	Public Booking API
Creates	A lead in the Leads tab	A scheduled order or a lead
Effort	Copy-paste snippet	Custom front-end code
Scheduling	None — follow up manually	Real availability; an order reserves time, while a lead records the requested time for follow-up
Pricing/services	Not shown	Full services, body-type pricing, memberships
CAPTCHA	Not required	Cloudflare Turnstile required on submit

Use lead capture when you just want inquiries to flow into the CRM. Use the shared native runtime for the supported booking experience on a bespoke website. Build directly against the Booking API only when you need a fully custom client.

​How it works

​The embed snippet

​WordPress with Contact Form 7

​You probably don’t need to rename your fields

​Everything else still reaches you

​Which submissions are forwarded

​WooCommerce orders

WooCommerce webhooks

​Posting directly

​Fields

​Response

​Booking API vs. lead capture

How it works

The embed snippet

WordPress with Contact Form 7

You probably don’t need to rename your fields

Everything else still reaches you

Which submissions are forwarded

WooCommerce orders

Posting directly

Fields

Response

Booking API vs. lead capture