Receive the ADF 1.0 XML payload, typically delivered as the body of an email to a designated inbox or via an HTTP POST to your inbound lead endpoint; validate the XML against the ADF 1.0 schema.
Parse the root element and extract the prospect block for customer details: name (first and last), contact elements (email, phone), and address.
Extract the vehicle block to get the interest elements: make, model, year, trim, condition (new or used), and any customer comments.
Extract the vendor block for the originating source or dealership details, and capture the requestdate element for lead timestamp.
Map the parsed fields to your CRM's lead object schema, deduplicating against existing records by email or phone before inserting.
Respond to the lead source with an acknowledgment; for HTTP POST delivery, return a 200 status; for email-based delivery, send a confirmation reply if required by the lead provider's SLA.
Known gotchas
ADF 1.0 is the dominant standard in production; a revised ADF 2.0 specification has been in draft since 2017 but is not widely deployed — do not expect 2.0 elements in real-world lead feeds without explicit confirmation from the lead provider.
Lead providers frequently send non-conforming ADF XML with missing required fields, unescaped special characters in comments, or extra whitespace; your parser must handle malformed XML gracefully rather than hard-failing.
The requestdate element uses a non-standard datetime format in some implementations; normalize dates to UTC during parsing and do not assume ISO 8601 compliance.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp