Field mapping

Feature Snapshot

Summary:
Field Mapping is the process of translating external data field names into standardized internal names within your lead flow, ensuring that all incoming data is consistent and ready for processing.

Key Benefits:

• Consistency – Standardizes varied input names from different sources into a single unified structure.
• Simplified Data Processing – Creates a uniform data model that downstream rules, filters, and integrations can reliably use.
• Improved Data Quality – Reduces errors and misinterpretations by aligning all field names to a defined standard.

Typical Use Cases:

• Inbound Field Mapping – Converting vendor, web form, or API field names into standardized internal names.
• Outbound Field Mapping – Transforming internal field names to match the expectations of external recipient systems.
• Integration Scenarios – Seamlessly integrating with CRMs, marketing platforms, and other systems by ensuring consistent field nomenclature.

How the Field Mapping works?

Step‑by‑Step Instructions

1. Access Your Flow’s Sources: Open your flow editor and navigate to the Sources step. If you are working with a new flow, click the Save button before proceeding.
2. Add or Edit a Field Mapping: Click the “Add Mappings” link next to the source you wish to configure. If mappings have already been created, click the “# Mapping(s)” link to review or update them.
3. Select the Standard Field: For each field submitted by your source, choose the corresponding standardized field from the dropdown menu on the left.
4. Enter the Source Field Name: In the adjacent text box on the right, type # and the exact field name as submitted by the source. Press Enter or click the “Insert as source field” option to confirm, ensuring a dynamic field placeholder is created.
5. Save Your Flow: Once all necessary fields are mapped, click Save at the top right to record your changes.

Expected Result:
Your flow will display a list of mappings that link each standardized field with its corresponding external field name. Upon lead submission, the system translates incoming field names to these standardized names, ensuring consistent downstream processing.

Validation & Monitoring (optional)

• Test the Setup: Submit a test lead from your external source and verify in the Events tab that all mapped fields display with the correct standardized names.
• Where to Monitor?: Check the lead details in the Events log to catch any mismatches in field mappings.

Best Practices

• Map every field that your source provides to ensure complete data capture.
• Always use standardized (default) field names whenever available to maintain uniformity across your flow.
• Confirm each mapping by ensuring the text converts into a dynamic placeholder (visually indicated, e.g., by a distinct colored background).
• Document any custom mappings or source-specific nuances so that future maintenance is streamlined.

Troubleshooting

Frequently Asked Questions (FAQ)

What is Field Mapping?

Field Mapping is the process of linking external field names—from vendors, web forms, or APIs—to standardized internal field names, ensuring that all incoming data is processed uniformly.

Why is Field Mapping important?

It ensures consistency across diverse data inputs, simplifies downstream processing such as filtering and integration, and improves overall data quality by minimizing errors due to mismatched field names.

How do I use Field Mapping in my flow?

In the Sources step of your flow editor, click “Add Mappings” next to your desired source, select the appropriate standardized field from the dropdown, enter the exact external field name, confirm the entry by pressing Enter or the “Insert as source field” option, and then save your flow.

What should I do if a mapped field doesn’t display correctly in my lead record?

Verify that the mapping was confirmed (i.e., the text converted into a dynamic placeholder) and double-check for any typographical errors in the field name. Ensure that the external field name exactly matches what is being sent.

Glossary