Map webhook fields and verify incoming leads

Start with a real example payload

Open the connection’s Field Mapping action. Paste a sample of the JSON object your external service will actually send into Sample Payload, then select Parse Fields. This reads possible source paths; it does not send a lead or create an application.

To try the mapping controls, copy this valid JSON into Sample Payload. The name, email, phone, and city are fictional examples. Replace them with authorized test data before sending an actual test delivery.

{
  "contact": {
    "email": "james.smith@truckersdata.com",
    "first_name": "James",
    "last_name": "Smith",
    "phone": "+12125550123"
  },
  "city": "Dallas"
}

Select Parse Fields, then add these five mappings. In Target Field, find the named group and select the field label shown below.

Save the mapping after selecting all five pairs. The email mapping is required. If your sender uses a different structure, use its actual source paths instead: an email inside a contact object becomes contact.email, while an email inside a fields object becomes fields.email. Changing the sample does not reformat the sender’s requests.

Build a mapping that can create an application

1. Paste a valid sample object and use Parse Fields.
2. For the first row, choose the sender’s actual email source and Applicant → Email as its target.
3. Use Add mapping for each additional value. Map identity and contact fields before optional application details.
4. Map custom answers under the Custom target group after creating their definitions in this company’s Custom Fields tab.
5. Remove incomplete rows and check for conflicting targets. A target represents one destination value, not a list of independent answers.
6. Save the mapping. The form checks that required target mappings, including Email, exist.
7. Send one known lead from the external sender using the same JSON structure and authentication.
8. Search Applications for that email and inspect the resulting values. Then test one deliberately invalid record so the sender’s error handling can be checked before normal use.

Understand the mapping controls

Targets and suitable values

What a successful lead import does

A processed lead creates a submitted application for the company that owns this connection. Its applicant is matched by email, and configured values are used to fill supported details. A matching previous application can supply prior information, so inspect the complete result rather than assuming that every displayed value came from this one request.

An imported lead is not proof that the driver completed the full application wizard, provided complete employment history, accepted every consent, or drew a signature. Your recruiting team must review those items. See employment verification and consent workflows for the next steps.

Changing a mapping affects subsequent processing. It does not revise every existing application. Required custom-field flags in the internal editor are not automatically required import rules; the import still requires its configured email target and validates supported mapped types.

Interpret processing outcomes