LoneScale integration

Overview

LoneScale is a sales intelligence platform that detects buying signals. This tool allows creating lists of contacts or companies, and adding items to those lists. Supported operations: List > Create, Item > Create for contacts, and Item > Create for companies. The tool filters empty fields from request bodies, sending only non-empty values.

Node Type

Action — processes input items and produces output

Input / Output

Direction	Port(s)
Input	Input
Output	Output, Error

Credentials

This tool requires LoneScale API credentials. See the Credentials Guide for setup instructions.

Resources

Resource	Value
List	list
Item	item

Operations

Each resource offers a single operation, and the two use different values — a list is created with create, an item with add.

Operation	Value	Description
Create	create	Create a list
Create	add	Create an item

Parameters

List: Create (create)

Parameter	Type	Required	Default	Description
Name	string	Yes	—	Name of your list.
Type	options	Yes	COMPANY	Type of your list.
				Options: COMPANY (a list of companies), PEOPLE (a list of contacts)

Item: Create (add)

Parameter	Type	Required	Default	Description
Type	options	Yes	PEOPLE	Type of your list. Selects which fields below apply.
				Options: COMPANY (a list of companies), PEOPLE (a list of contacts)
List ID	string	Yes	—	ID of the target list. Find list IDs in the LoneScale dashboard or use the API to list available lists.
First Name	string	Yes	—	Contact first name. (shown when Type is PEOPLE)
Last Name	string	Yes	—	Contact last name. (shown when Type is PEOPLE)
Additional Fields (peopleAdditionalFields)	collection	No	{}	Extra contact detail sent with the item. (shown when Type is PEOPLE)
— Full Name	string	No	—	Contact full name.
— Contact Email	string	No	—	Contact email address.
— Company Name	string	No	—	Contact company name.
— Current Position	string	No	—	Contact current position.
— Company Domain	string	No	—	Contact company domain.
— LinkedIn URL	string	No	—	Contact LinkedIn URL.
— Contact Location	string	No	—	Contact location.
— Contact ID	string	No	—	Contact ID from your source.
Company Name	string	No	—	Company name. (shown when Type is COMPANY)
Additional Fields (companyAdditionalFields)	collection	No	{}	Extra company detail sent with the item. (shown when Type is COMPANY)
— LinkedIn URL	string	No	—	Company LinkedIn URL.
— Company Domain	string	No	—	Company domain.
— Contact Location	string	No	—	Company location.
— Contact ID	string	No	—	Contact ID from your source.

All Operations

Parameter	Type	Required	Default	Description
Max Concurrency	number	No	10	Maximum number of items to process concurrently.

Output Data

One output item per input item, for both operations. The item JSON is replaced by LoneScale’s response — the fields you sent in are not carried through, so capture anything you still need before this node. Binary data on the input item is forwarded.

• List: Create returns the created list record. Take the new list’s ID from it and feed it into a following Item node’s List ID.
• Item: Create returns the created item record.

If LoneScale answers with something that is not a JSON object, the response is wrapped instead:

{
  "result": "..."
}

The record’s own fields are whatever LoneScale returns; the node does not rename, nest or filter them. Reference them downstream by expression, e.g. {{ $json.id }}.

Note that the two Type-specific field sets are mutually exclusive: with Type set to PEOPLE, the company fields are not sent, and vice versa. Empty fields are dropped from the request entirely rather than sent as blanks.

Example Configuration

Create a contact list:

{
  "type": "lonescale",
  "parameters": {
    "resource": "list",
    "operation": "create",
    "name": "Q4 Prospects",
    "type": "PEOPLE"
  }
}

Create a company list:

{
  "type": "lonescale",
  "parameters": {
    "resource": "list",
    "operation": "create",
    "name": "Target Enterprises",
    "type": "COMPANY"
  }
}

Add a contact to an existing list, with enrichment data carried from upstream:

{
  "type": "lonescale",
  "parameters": {
    "resource": "item",
    "operation": "add",
    "type": "PEOPLE",
    "list": "{{ $json.listId }}",
    "first_name": "{{ $json.firstName }}",
    "last_name": "{{ $json.lastName }}",
    "peopleAdditionalFields": {
      "email": "{{ $json.email }}",
      "company_name": "{{ $json.company }}",
      "current_position": "{{ $json.title }}",
      "domain": "{{ $json.domain }}",
      "linkedin_url": "{{ $json.linkedin }}",
      "location": "{{ $json.city }}"
    }
  }
}

Add a company to an existing list:

{
  "type": "lonescale",
  "parameters": {
    "resource": "item",
    "operation": "add",
    "type": "COMPANY",
    "list": "{{ $json.listId }}",
    "company_name": "{{ $json.company }}",
    "companyAdditionalFields": {
      "linkedin_url": "{{ $json.linkedin }}",
      "domain": "{{ $json.domain }}",
      "location": "{{ $json.location }}"
    },
    "maxConcurrency": 20
  }
}

Error Handling

Mode	Behavior
stop	Halts workflow on first error
continue	Skips failed items, passes successful ones through
errorPort	Routes failed items to Error output port

Tips

This tool creates lists and adds contacts or companies to LoneScale prospect lists. It is ideal when you need to organize sales leads or companies within LoneScale, rather than retrieving information or performing other sales-related tasks. The tool produces a new list or adds a specified item to an existing list within LoneScale.

Parameter Relationships

Resource-Operation Dependencies

• When resource = "list": Only "create" operation is available
• When resource = "item": Only "add" operation is available

Type-Specific Field Dependencies

• When adding "PEOPLE" items: first_name, last_name, and peopleAdditionalFields become available
• When adding "COMPANY" items: company_name and companyAdditionalFields become available

List Management Best Practices

• Use descriptive list names that reflect the prospect segment
• Choose appropriate list types (PEOPLE vs COMPANY) based on your sales process
• Leverage additional fields to store enrichment data from other sources