Overview
The LoneScale List node for n8n allows you to add a new item (such as a contact or company) to an existing LoneScale list. This is useful for automating the enrichment and management of your contact or company databases within LoneScale from n8n workflows.
Common scenarios:
- Automatically adding new leads or contacts collected from forms, CRMs, or other sources into a LoneScale list.
- Enriching company data by pushing new company records into LoneScale for further processing.
- Integrating LoneScale with other tools in your automation stack for seamless data flow.
Example:
When a new lead is captured via a web form, this node can be used to add the lead's details (name, email, LinkedIn URL, etc.) directly to a LoneScale contact list.
Properties
| Name | Type | Meaning |
|---|---|---|
| Type | options | Specifies whether the item is a "Company" or "Contact". Determines the type of list used. |
| List Name or ID | options | The target LoneScale list to which the item will be added. Can select from available lists or specify an ID. |
| First Name | string | Contact's first name. |
| Last Name | string | Contact's last name. |
| Full Name | string | Contact's full name. |
| Linkedin Url | string | Contact's LinkedIn profile URL. |
| Company Name | string | Name of the company associated with the contact. |
| Current Position | string | Contact's current job position. |
| Company Domain | string | Domain of the company associated with the contact. |
| Contact Location | string | Geographical location of the contact. |
| Contact Email | string | Email address of the contact. |
| Contact ID | string | An external identifier for the contact (from your source system). |
Output
The node returns the response from the LoneScale API after attempting to add the item. The output structure is a JSON object containing the result of the operation. The exact fields depend on the LoneScale API response, but typically include information about the newly added item or any errors encountered.
Example output:
[
{
"id": "12345",
"first_name": "John",
"last_name": "Doe",
"email": "john.doe@email.com",
"status": "added",
// ...other fields returned by LoneScale
}
]
Dependencies
- External Service: Requires access to the LoneScale API.
- API Key: You must provide a valid LoneScale API key via n8n credentials (
loneScaleApi). - n8n Configuration: No additional configuration required beyond setting up the credential.
Troubleshooting
Common issues:
- Invalid API Key: If the API key is missing or incorrect, the node will fail with an authentication error. Ensure your
loneScaleApicredential is set up correctly in n8n. - Missing Required Fields: If required properties (like "Type" or "List Name or ID") are not provided, the node will throw an error. Double-check that all mandatory fields are filled.
- List Not Found: If the specified list does not exist or the ID is incorrect, the API may return a "not found" error.
- API Rate Limits: Excessive requests may trigger rate limiting by LoneScale.
Error messages and resolutions:
"401 Unauthorized": Check your API key and permissions."404 Not Found": Verify the List ID or ensure the list exists in LoneScale."400 Bad Request": Review input fields for missing or invalid values.