Field Mapping

Configure how data flows into and out of Ledly by mapping fields at each stage.

Overview

Ledly uses a two-stage field mapping system:

Inbound Mapping - Map fields from vendors and lead sources to Ledly’s standard schema
Outbound Mapping - Map Ledly fields to your CRM (Salesforce) or custom endpoints

Both inbound and outbound mappings must be configured before leads can flow through the system.

Inbound Mapping

Map incoming lead fields from vendors and forms to your standard Ledly schema.

Why Inbound Mapping?

Different lead sources use different field names:

Vendor A sends firstName, Vendor B sends first_name
Some sources use emailAddress, others use email

Inbound mapping normalizes all data to a consistent format.

Creating an Inbound Map

Go to Settings → Field Mapping → Inbound
Select the lead source you want to map
For each source field, select the corresponding Ledly field
Click Save

Example Inbound Mapping

Source Field	Ledly Field
`firstName`	`first_name`
`lastName`	`last_name`
`emailAddress`	`email`
`cellPhone`	`phone`
`programOfInterest`	`program_code`

Default Values

Set default values for fields that aren’t provided by the source:

Static Value: Always use a specific value (e.g., source = "Vendor A")
Source Name: Automatically use the lead source name
Current Date: Use the timestamp when the lead was received

Transformations

Apply transformations to incoming data:

Transformation	Description	Example
Lowercase	Convert to lowercase	`JOHN` → `john`
Uppercase	Convert to uppercase	`john` → `JOHN`
Trim	Remove leading/trailing whitespace	`john` → `john`
Phone Format	Standardize to E.164	`(555) 123-4567` → `+15551234567`
Title Case	Capitalize first letters	`john doe` → `John Doe`

Outbound Mapping

Map Ledly fields to your destination - Salesforce, custom endpoints, or other CRMs.

Why Outbound Mapping?

Your CRM may use different field names or have custom fields:

Salesforce uses FirstName, Ledly uses first_name
You may have custom Salesforce fields like Program_Interest__c

Outbound mapping ensures data lands in the right place.

Salesforce Field Mapping

Go to Settings → CRM Integration → Field Mapping
For each Ledly field, select the Salesforce field to map to
Click Save Mapping

⚠️

You must connect to Salesforce before configuring field mapping. See the Salesforce Integration guide.

Standard Salesforce Mappings

Ledly Field	Salesforce Lead Field
`email`	`Email`
`first_name`	`FirstName`
`last_name`	`LastName`
`phone`	`Phone`
`company`	`Company`

Custom Salesforce Fields

Map Ledly fields to custom Salesforce fields:

Ledly Field	Salesforce Field
`program_code`	`Program_Interest__c`
`start_date`	`Preferred_Start_Date__c`
`lead_source`	`Lead_Source_Detail__c`

Custom Endpoint Mapping

For webhook or API destinations:

Go to Settings → Webhooks → Select your endpoint
Click Configure Payload
Map Ledly fields to your desired JSON structure
Click Save

Example custom payload template:

{
  "contact": {
    "email": "{{email}}",
    "name": "{{first_name}} {{last_name}}",
    "phone": "{{phone}}"
  },
  "interest": {
    "program": "{{program_code}}",
    "source": "{{lead_source}}"
  }
}

Mapping Workflow

The complete lead flow with field mapping:

Vendor/Source → Inbound Mapping → Ledly → Outbound Mapping → Salesforce/Endpoint
     |                |              |              |                |
  Raw fields    Normalized to    Stored in     Mapped to CRM      Delivered
                Ledly schema     database      field names

Best Practices

Map all required fields first - Ensure email and other required fields are mapped before testing
Test with sample leads - Use the test feature to verify mappings before going live
Document custom fields - Keep a record of custom field mappings for your team
Review regularly - Update mappings when adding new lead sources or CRM fields

Troubleshooting

Leads not appearing in Salesforce

Verify outbound mapping is configured
Check that required Salesforce fields are mapped
Review the sync log for errors

Field values are empty

Confirm the source is sending the expected field names
Check inbound mapping for the lead source
Verify transformations aren’t clearing values

Custom fields not syncing

Ensure the Salesforce field API name is correct (ends with __c)
Verify field-level security allows the connected user to write to the field
Check that the field type matches (text to text, date to date, etc.)

Overview Lead Validation