Available Fields

The records you send to CRM Sync are free-form JSON objects. Their keys are LoneScale field keys, the same vocabulary your CRM integration mapping is built on. Two rules decide what actually reaches your CRM:

LoneScale only reads the keys your mapping references. A key you send that no mapped field and no unicity criterion points at is ignored.
A record whose keys match none of them is failed rather than silently written as a no-op, and the error lists the keys that mapping expects.

Call GET /crm/mapping to see exactly which of the fields below your own mapping uses, before pushing anything.

The prefix is optional. Every key below can be sent without its lonescale_ or main_ prefix: first_name, job_title, company_domain, email, phone. Both forms work, and the bare one never overrides a prefixed key you sent explicitly.

People

Field key	Description
`lonescale_first_name`	First name
`lonescale_last_name`	Last name
`lonescale_full_name`	Full name
`lonescale_linkedin_url`	LinkedIn profile URL
`lonescale_universal_name`	LinkedIn public identifier (the slug in the profile URL)
`lonescale_job_title`	Job title
`lonescale_job_seniority`	Seniority level
`lonescale_department`	Department
`lonescale_sub_department`	Sub-department
`lonescale_level`	Hierarchical level
`lonescale_summary`	Profile summary
`lonescale_city`	City
`lonescale_geo_location_name`	Location name
`lonescale_geo_country_name`	Country name
`lonescale_country_code`	Country code

Contact details

Field key	Description
`main_email`	Primary email
`main_email_status`	Deliverability status of the primary email
`secondary_emails`	Additional emails
`secondary_emails_status`	Deliverability status of the additional emails
`main_phone`	Primary phone
`main_phone_region`	Region code of the primary phone
`secondary_phones`	Additional phones
`secondary_phones_region`	Region codes of the additional phones

Company

Company keys can be embedded on a contact record (to create or update the associated account at the same time) or sent on their own in the companies array.

Field key	Description
`lonescale_company_name`	Company name
`lonescale_company_domain`	Company domain
`lonescale_company_description`	Company description
`lonescale_company_industry`	Industry
`lonescale_company_linkedin_url`	Company LinkedIn URL
`lonescale_company_linkedin_id`	Company LinkedIn id
`lonescale_company_staff_count`	Employee count
`lonescale_company_employee_range`	Employee range
`lonescale_company_country`	Country
`lonescale_company_country_code`	Country code

CRM ids

Field key	Description
`contact_crm_id`	Update this exact CRM contact by id (for example the id returned by `POST /crm/search`), skipping unicity matching
`account_crm_id`	Target this exact CRM company by id instead of matching by unicity criteria
`crm_company_id`	The associated company id, available to your mapping as a value to write

Accepted aliases

Field keys are resolved before the mapping runs, so several spellings of the same field work. Without the prefix. Drop lonescale_ or main_ from any key in the tables above and it still resolves: first_name, full_name, job_title, linkedin_url, department, city, country_code, company_name, company_domain, company_staff_count, email, email_status, phone, phone_region. Person and company keys stay distinct: city is the contact’s, company_city is the account’s. From an enrich payload. You can also send our enrich output verbatim.

You send	Resolved to
`firstName`, `lastName`, `fullName`	`lonescale_first_name`, `lonescale_last_name`, `lonescale_full_name`
`linkedinUrl`, `universalName`	`lonescale_linkedin_url`, `lonescale_universal_name`
`jobTitle`	`lonescale_job_title`
`email`, `emailStatus`	`main_email`, `main_email_status`
`phone`, `phoneCountryCode`	`main_phone`, `main_phone_region`
`lonescale_email`, `lonescale_phone`	`main_email`, `main_phone`
`companyName`, `companyDomain`, `companyDescription`, `companyIndustry`	the matching `lonescale_company_*` key
`companyEmployeeCount`, `companyEmployeeRange`	`lonescale_company_staff_count` and `lonescale_company_employee_count`, `lonescale_company_employee_range`
`companyLinkedinUrl`, `companyLinkedinId`, `companyCity`, `companyCountry`, `companyCountryCode`	the matching `lonescale_company_*` key
any bare `company_*` key	the matching `lonescale_company_*` key

An alias never overwrites a key you sent explicitly.

Salesforce: Contacts or Leads

For Salesforce, the mapping also decides which object is written, exactly like in a workflow. No parameter on the request controls it:

Map the Contact section and the sync writes Contacts.
Map only the Lead section, leaving the Contact one empty, and the sync searches your Lead unicity criteria, then updates the match or creates a Lead.

GET /crm/mapping reports this as object: "contact" or object: "lead", and returns the resolved lead mapping alongside it.

Salesforce requires Company on Lead creation, so map it from lonescale_company_name and send that key on every record that may create a Lead.

Example

{
  "crm": "salesforce",
  "settings_type": "api_sync",
  "contacts": [
    {
      "first_name": "Ada",
      "last_name": "Lovelace",
      "job_title": "Head of Data",
      "linkedin_url": "https://www.linkedin.com/in/ada-lovelace",
      "email": "ada@acme.com",
      "phone": "+33600000000",
      "company_name": "Acme",
      "company_domain": "acme.com"
    }
  ]
}

The same record written as lonescale_first_name, main_email and so on is equivalent.

Getting Started

API Enrichment

Companies

CRM Sync

Webhooks

Lists

Webhook Payload

People

Contact details

Company

CRM ids

Accepted aliases

Salesforce: Contacts or Leads

Example

​People

​Contact details

​Company

​CRM ids

​Accepted aliases

​Salesforce: Contacts or Leads

​Example

People

Contact details

Company

CRM ids

Accepted aliases

Salesforce: Contacts or Leads

Example