XML integration

What is XML Integration?

XML Integration in LeadConduit enables you to extract, map, and process nested XML submissions from your lead sources. It works by analyzing the XML’s hierarchical structure—including nested elements, attributes, and even namespaced tags—and converting these into dynamic field placeholders through dot notation. This integration supports both element values and their appended attributes, ensuring that every piece of lead information is properly captured and made available for further processing in your flow.

Why is XML Integration Important?

XML submissions are common with many lead vendors and partners; they often present data in complex, nested formats. Using XML Integration is critical because it:

• Ensures that no data is lost—even when submissions include deeply nested elements or attributes;
• Provides robust handling of optional XML variations, such as namespaced tags or XML arrays, so that every detail is accurately mapped;
• Enables downstream enhancements, validation, and decision-making by transforming structured XML into dynamic lead fields, ultimately improving lead quality and operational efficiency.

How do I use the XML Integration?

1. Identify the XML Structure:

   • Examine a sample XML submission to understand its hierarchy. For example, an XML payload might include a nested structure with separate elements for contact details and address information.
   • Note the location of each value, including any XML attributes that may be appended to elements.

2. Map Nested Elements Using Dot Notation:

   • In your flow’s Sources step, create inbound field mappings by entering dot notation paths that mirror the XML hierarchy (e.g., contact.personal.first_name, contact.email, address.city).
   • After typing a mapping, press Enter or click the “+” button so it converts into a dynamic field placeholder (indicated by a green background), ensuring that the field is treated as variable data.

3. Handle Optional XML Variations:

   • For submissions with namespaces, use the syntax /*[name()='soap:Envelope']/*[name()='soap:Body']/*[name()='CreateResponse'] to have the parser ignore namespace prefixes and match nodes by their local names.
   • If your XML includes repeated elements (arrays), ensure that the source sends these as separate properties (for instance, phone_1 and phone_2) since individual array element mapping is not supported.

4. Test Your Mappings:

   • Submit a test XML payload to the designated source endpoint and verify in the Events tab that each mapped field is populated with the correct value extracted from the nested XML structure.
   • Review the raw XML and technical details if any mapped field remains empty or if errors such as “string.trim is not a function” occur, and adjust the dot notation paths to match exact element names and cases.

5. Validate and Troubleshoot:

   • Confirm that all mapping paths exactly match the XML structure (keeping in mind XML’s case sensitivity).
   • Use XML validation tools if necessary, and test with various sample payloads to capture edge cases such as null values or unwanted characters.
   • Document your mappings and any special cases so that future integrations or troubleshooting are streamlined.

By following these steps and best practices, you can confidently integrate and process complex XML submissions in LeadConduit—ensuring every lead is accurately captured and enriched for downstream use.