Field types

Leandro
Leandro
  • Updated

Feature Snapshot

Summary:
Field Types in LeadConduit are predefined data formats assigned to lead fields that govern how data is validated, formatted, and processed, ensuring consistency and integrity across integrations.

Key Benefits:

  • Ensures data integrity by performing automatic validation on lead inputs.
  • Standardizes data formats to streamline integration with CRMs and external systems.
  • Minimizes processing errors by rejecting values that do not match predefined formats.

Typical Use Cases:

  • Defining the data format (e.g., Email, Phone, Date) when setting up fields in your flow.
  • Validating that user input (such as phone numbers or postal codes) adheres to a standardized format.
  • Mapping and transforming lead data for downstream delivery to recipient systems.

How the Field Types work?

Field Types determine the expected content for each field within your LeadConduit flow. When a field is assigned a type—for example, “Email” or “Phone”—LeadConduit automatically enforces rules such as correct formatting and valid data patterns. This systematic approach not only improves data quality but also ensures that the flow integrates smoothly with external systems by delivering standardized values.

Step‑by‑Step Instructions

  1. Access the Fields step:
    Open your LeadConduit flow and navigate to the desired flow. Click on the Fields step at the top of the flow editor.

  2. Select or Create a Field:
    Add/Remove any fields from your Flow with the toggle next to each field name. Or go to Add to Flow > Flow Field to create a new field that will capture the desired data.

  3. Assign a Field Type:
    In the field settings, select the appropriate Field Type from the dropdown list. Common Field Types include:

    • Email – Validates that the input matches standard email structure.
    • Phone – Ensures numeric input and formats phone numbers correctly.
    • Postal Code – Enforces patterns for ZIP or postal codes.
    • Date – Validates that dates are entered in a recognized format.
    • Number – Accepts only numeric values.
    • String – Allows free-form text without predefined formatting.
    • Boolean – Accepts true/false values.
  4. Save the Field Configuration:
    Click Save to confirm your settings. The chosen Field Type then automatically applies its validation to all incoming data for that field.

Expected Result:
When a lead is submitted, each field accepts only data that conforms to its assigned type. For instance, an “Email” field will reject improperly formatted email addresses, while a “Phone” field will only accept numeric values in the appropriate format.

custom field creation modal


Validation & Monitoring (optional)

  • Test the Setup: Submit test leads with both valid and invalid entries for each field type to ensure validation is functioning properly.
  • Where to Monitor?: Review the Events tab in your LeadConduit account to monitor error messages and data formatting outcomes.

Best Practices

  • Always select a standard Field Type when available to guarantee built-in validation and seamless integration.
  • Use clear and descriptive field names (e.g., contact_email or primary_phone) to avoid confusion during troubleshooting.
  • Test field behavior with a variety of input examples to confirm that each Field Type enforces the proper restrictions.
  • For fields requiring custom formatting, consider using a Custom Field with additional validation rules, keeping in mind that custom fields may not benefit from all automatic checks.

Troubleshooting

Symptom / Error Likely Cause Resolution
Field accepts improperly formatted data Incorrect Field Type selected or misconfigured Revisit field settings and select the appropriate Field Type; retest with valid sample data.
Field value is unexpectedly rejected Input data does not match the constraints of the Field Type Verify that the input adheres to the required format; adjust the input or field settings accordingly.
Custom Field lacks proper validation Custom fields do not have built-in validations like standard fields Consider switching to a standard Field Type or supplement with additional custom validation rules.

Frequently Asked Questions (FAQ)

What are Field Types in LeadConduit?

Field Types are predefined data formats that specify the expected content for each field in a lead flow, enforcing validation rules and ensuring consistency across data submissions.

Why is it important to use Field Types?

Using Field Types helps maintain data integrity by automatically checking that entries conform to expected formats, thereby reducing errors during data processing and improving integration consistency with external systems.

How do I assign or change a Field Type for a field?

In the flow editor, navigate to the Fields step, select the desired field, then choose the appropriate Field Type from the dropdown menu. After making your selection, save the configuration to enforce the new rules.

What happens if a user enters data that does not match the selected Field Type?

The system will either reject the invalid input or flag it as an error based on the pre-established validation rules for that Field Type, ensuring that only properly formatted data is accepted.

What is a TrustedForm Cert URL Field Type?

A TrustedForm Cert URL Field Type in LeadConduit is a special field that instantly validates whether a TrustedForm certificate URL is real and not expired, allowing bad or fake certificates to be rejected before a lead is processed. It also provides detailed certificate information through sub-components and operators, giving users deeper insight into the certificate even without a TrustedForm subscription.


Glossary

Term Definition
Field Type A predefined data format assigned to a field that enforces specific validation and formatting rules.
Validation The process of ensuring that input data conforms to the expected format defined by the Field Type.
Standard Field A field provided by LeadConduit with built-in validation and standard naming conventions for easy integration.
Custom Field A user-defined field created for specific needs that may require manual validation rules beyond standard types.

Was this article helpful?

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.