Build the form
Drag in the fields your sales floor actually needs: name, contact, vehicle interest, trade-in, ZIP. Same Formester builder you would use for any other form.
Build the form in Formester. Paste your CRM's lead intake email. Map fields once. The next submission lands as a structured prospect, no manual entry and no Zapier chain.
Connect Formester to VinSolutions, DealerSocket, CDK, and every automotive CRM that accepts ADF/XML. One connector, configured once per form.
VinSolutions

DealerSocket

CDK Global

Reynolds and Reynolds

DriveCentric

ProMax
Keyloop
AutoRaptor
eLEAD
If your CRM has a lead intake email address that accepts ADF/XML, Formester will work with it. Almost every dealership-grade CRM does. The integration is to the format, not the brand.
Map any of these to a form question once, and Formester routes every submission into the matching ADF node. Covers customer details, vehicle interest, and your dealership's vendor block.
Who the lead is, how to reach them, and what they wrote.
What the customer is asking about. Repeat the block for a trade-in.
Your dealership block. Filled in once in Formester, sent with every lead.
Left: a Formester form on a dealership site. Right: the byte-for-byte email Formester sends when it is submitted. Copy the XML, hand it to your CRM admin, they will recognize it.
A specialist will get back to you within an hour during business hours.
<?xml version="1.0" encoding="UTF-8"?><adf><prospect status="new"><requestdate>2026-05-26T14:32:11-05:00</requestdate><vehicle interest="buy" status="used"><year>2024</year><make>Toyota</make><model>RAV4</model></vehicle><!-- trade-in repeats the vehicle block --><vehicle interest="trade-in" status="used"><year>2018</year><make>Honda</make><model>CR-V</model><odometer>62000</odometer></vehicle><customer><contact><name part="first">Jordan</name><name part="last">Reyes</name><email>jordan.reyes@example.com</email><phone type="voice">(512) 555-0143</phone><address> <postalcode>78704</postalcode></address></contact><comments>Looking for a low-mileage AWD. Trading in a 2018 Honda CR-V, 62k miles, clean title.</comments></customer><vendor><vendorname>Hill Country Toyota</vendorname></vendor></prospect></adf>
Build the form, paste your CRM's intake email, map fields and test. Per-CRM walkthroughs (VinSolutions, DealerSocket, CDK, others) live in the docs.
Drag in the fields your sales floor actually needs: name, contact, vehicle interest, trade-in, ZIP. Same Formester builder you would use for any other form.
Open Automate, Integrations, Automotive CRM. Paste the CRM intake email. Connect SMTP so leads send from your own domain.
Drop your form questions onto ADF nodes. Translate values where they differ ("SUV" to bodystyle). Send a test lead. Save.
The three ways dealerships move web leads into a CRM today. Side by side, on what actually matters at the end of the month.
| Capability | Formester | Zapier chain | Manual entry |
|---|---|---|---|
| Per-lead cost What this costs as lead volume scales. |
Flat plan
No per-lead fee. Volume on a Friday does not surprise you on the invoice.
|
Per-task
Each step counts, code steps cost more, volume on a Friday stings.
|
BDC time
Paid in hours. Always more than you think once you measure it.
|
| Real ADF/XML format Does the lead land as a structured ADF prospect? |
Native
Spec-conformant
<adf> email. Your CRM parses it as a real prospect. |
JSON in email
Sends JSON in the body or attached as a file. Most CRMs ignore it.
|
Free text
Vehicle, trade-in, ZIP, everything ends up smushed in a single notes field.
|
| Value mapping Translate form answers to ADF values. |
Built in
Map
"SUV" to vehicle status="used" on the same screen, no code step. |
Code step
A formatter or Code-by-Zapier step per translation. One per CRM, per form.
|
BDC judgement
Whichever BDC rep is on call decides what the answer maps to.
|
| Send from your domain Does the lead leave from your dealership's email server? |
SMTP
Google Workspace, Microsoft 365, SendGrid, Postmark, anything that speaks SMTP.
|
Shared sender
Default sender is a shared Zapier address. Custom domain takes extra setup.
|
Yes
Comes from whichever rep typed it. Useful but not consistent.
|
| BCC managers Loop in sales managers automatically. |
Per-form
Add BCC addresses on each form. Sent on every lead, no human in the loop.
|
Extra step
Second Zap or a duplicate path. More tasks billed, more places to break.
|
Forwarded
The BDC rep remembers to forward. Sometimes.
|
| Setup time From signed-up to first lead in CRM. |
Minutes
Build form, paste intake email, map and test. Once per CRM, then it runs.
|
Hours per Zap
Triggers, formatters, value translations, sender setup, then test on the right CRM.
|
None
No setup. Cost surfaces as ongoing salary instead.
|
Compliance covered the same way across all three: GDPR, UK GDPR, and CCPA. Data delivered over TLS.
Six questions we get from every dealership and lead vendor. Anything else, write to us directly.
ADF, the Auto-lead Data Format, is the XML schema the automotive industry settled on for moving sales leads between websites and CRMs. A lead is sent as an email with the XML in the body or as an attachment.
Every dealership-grade CRM has an intake address that parses these emails and creates a prospect record from the XML. It is not a new protocol, it is the one your CRM already speaks.
Yes if it accepts ADF/XML lead emails. Formester sends to the format, not the brand, so almost every dealership-grade CRM works.
Email support@formester.com with the CRM name and we will confirm within one business day.
Every automotive CRM that accepts ADF/XML lead emails. That includes VinSolutions, DealerSocket, CDK Global, Reynolds and Reynolds, DriveCentric, ProMax, Keyloop, AutoRaptor, eLEAD, and others.
The integration is to the format, not the brand, so new CRMs work the moment they expose an ADF intake email.
No. The integration is one ADF/XML connector, configured per form.
Switching from VinSolutions to DealerSocket means changing one email address in the form's automation settings.
Yes, through SMTP. Connect your dealership's outbound mail server (Google Workspace, Microsoft 365, SendGrid, Postmark, anything that speaks SMTP), enter the host, port, and credentials once, and every ADF lead leaves your server signed by your domain.
Your CRM sees the email coming from your sales address, not from a Formester relay, which keeps you off shared IP reputations and out of the spam folder.
Usually under Lead Sources, Lead Routing, or ADF Integrations in admin settings. The fastest path is to ask your CRM provider's support team for your ADF lead intake email address.
Build the form, paste your CRM's intake email, send a test lead. The next real submission lands in your CRM as a structured prospect.
Get started