LoneScale n8n integrationAutomate LoneScale with n8n.
Sales lists should not be typed by hand. The LoneScale n8n integration gives you a node with 2 operations across 2 resources, List and Item, plus a trigger that fires on a new event from the LoneScale workflow you pick by name. For teams that keep contact lists alive from a sheet, a CRM or a form.
Verified Trustpilot reviews · AI, automation & growth agency
What does the LoneScale n8n integration actually do?
The LoneScale node handles the list side of LoneScale from a workflow: it creates a list, then adds contacts or companies to it. Two resources, two operations, nothing to install. The LoneScale Trigger runs the other way round. It waits for a new event from one LoneScale workflow you select by name, and hands the payload to the rest of your n8n run.
Take the spreadsheet of contacts someone collected at a trade show. A Google Sheets node reads the rows, list.create opens a list of type Contact, and item.add writes one item per row with the first name, the last name and the email already sitting in the sheet. Nobody retypes anything, and the list exists in LoneScale before lunch.
Second result: a list that follows the CRM instead of drifting from it. Contacts that reach a given stage in Pipedrive or HubSpot leave on a scheduled run, and item.add drops each of them into a list created once. The target is picked by name in List Name or ID, or by ID through an expression when the name is not stable.
Third result: the team hears about a LoneScale event without opening LoneScale. The trigger fires, a message lands in the sales channel through Slack, and the same run writes the record wherever it belongs. This takes seconds, because the trigger is a webhook and not a scheduled check.
Two resources, two operations: that is the whole node, and it is worth knowing before you plan around it. Anything the LoneScale API exposes outside that catalog goes through the HTTP Request node, which calls the endpoint directly and reuses the same LoneScale credential through predefined authentication. One key, no second login to manage.
Two habits save time later. The trigger registers its webhook when the workflow is activated, so a draft left switched off collects nothing. And a field marked required really does block the node when it is empty, so map First Name and Last Name before you go live. If n8n is new to part of the team, the n8n training covers the expression syntax used above, and the n8n review puts the tool in context.
How do you connect LoneScale to n8n?
- 01
Generate your LoneScale API key
Start in LoneScale, not in n8n. The credential accepts one authentication method, an API key, so there is no OAuth dance and no app to approve. Create a LoneScale account if the team does not have one yet, then generate the key from the account, following the LoneScale public API article in their help center (reference 6454360). Copy it once and keep it somewhere safe for the next step.
- 02
Create the credential in n8n
In n8n, open the Credentials menu and add a new LoneScale credential. A credential is the stored login n8n uses to call a service for you, saved once and kept out of the workflow itself. Paste the key into the API Key field, then save. That single entry covers both the LoneScale node and the LoneScale Trigger, and every workflow you build later picks it from a dropdown.
- 03
Select the credential in the node
Drop the LoneScale node on the canvas and choose the credential at the top of the panel, then pick the resource, List or Item, and the operation. On the LoneScale Trigger, choose the LoneScale workflow in Workflow Name. When the trigger is the entry point of the run, activate the workflow: that is the moment n8n registers the webhook URL with LoneScale.
What starts a workflow from LoneScale ?
LoneScale Trigger is the node that starts a workflow each time LoneScale receives a new submission. Pick the form, activate the workflow: n8n registers the webhook on your LoneScale account.
What you see in n8n
Configuration notes
01Set up the LoneScale Trigger
This node is the entry point of the run. It waits for a new event from LoneScale and starts the workflow with whatever arrives. Version 1, one setting to fill, and the credential you already saved.
Key parameters
- Workflow Name: required. Select one workflow, chosen from the list. The trigger listens to that workflow and to no other, so two LoneScale workflows mean two trigger nodes on the canvas.
02On new LoneScale event
This is the single event the trigger exposes, and it carries the payload LoneScale sends into the first node of your run. What travels inside depends on the LoneScale workflow you selected in the setting above, so the honest move is to look at one real execution before mapping anything downstream.
{{ $json.field }} where field is the key you just saw. That is enough to chain a notification, a CRM record, or a second LoneScale call that pushes the contact into a list. Keep the workflow active between tests, since the webhook registration lives with the active state.What can the LoneScale node do?
The LoneScale node exposes 2 operations across 2 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.
List
1 operationCreate a list
list.createWhat you see in n8n
Notes & use cases
Creates a list in LoneScale and gives the rest of the workflow somewhere to write. Run it once, then feed it.
Key parameters
- Name: required, the name of your list, the label you will recognise later in LoneScale. The field shows
list nameas its placeholder. - Type: required, two values only.
COMPANYcreates a list of companies,PEOPLEcreates a list of contacts.
Item
1 operationCreate a item
item.addWhat you see in n8n
Notes & use cases
Adds one item to a list that already exists, on the contact side or the company side.
Key parameters
- Type: required,
COMPANYfor a list of company,PEOPLEfor a list of contact. - List Name or ID: required. Choose from the list, or specify an ID with an expression such as
{{ $json.field }}. - First Name and Last Name: required, the contact first name and last name.
- Company Name: optional, the contact company name.
- Additional Fields: 12 optional fields, including Contact Email, Current Position, Company Domain, Linkedin Url, Contact Location and Contact ID, the contact ID from your source.
Need help automating LoneScale with n8n?
A person reads every message.
