Event

trigger.lonescale_event

TriggerCRM & salesconnection requiredruns in-engine

Registers a hook on one LoneScale search at publish and starts one run per record delivered. Emits {id, workflow_id, payload}.

Start a run when a LoneScale search finds a person or company (job change, hiring intent).

Ask about LoneScale All LoneScale nodes Provider API docs ↗

Connection

Required: Yes — the node will not save without one
Auth type: API key
Providers: LoneScale
Secret shape: the LoneScale API key, or {"api_key": "…"}
Resolved by: config.connection_id, else node.connection_id
Note: Publishing needs MANTLE_APP_PUBLIC_BASE_URL set — it is the address LoneScale is told to POST to. Note that LoneScale neither signs its deliveries nor issues a shared secret, so the unguessable id in that callback URL is the only thing separating a real record from anything else posted to it.

Configuration

1 field, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

Field	Type	Required	Default	Constraints	Example
workflow_id The LoneScale search to listen to — its 'workflow' id. LoneScale calls its job-change and hiring-intent searches workflows; one hook belongs to one search. Read the ids with the LoneScale: List Workflows node.	string	Yes	—	—	wf_7d21

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "workflow_id": "wf_7d21"
}

Output

One shape.

lonescale record

LoneScale's record under `payload`, with an id lifted out where there is one. Open, because LoneScale publishes no schema for the hook body.

Extra keys beyond the ones listed can appear.

Field	Type	Example
id Whatever id LoneScale put on the record (id, _id, contact_id or event_id), and the idempotency key when there is one. Empty when the delivery carried none — LoneScale publishes no schema, so this cannot be promised.	string	c_9f3a1b2c
workflow_id The LoneScale search the record came from, when the body names it. Empty otherwise; the trigger already listens to exactly one search.	string	wf_7d21
payload LoneScale's record, verbatim. For a PEOPLE search this is a contact (names, current position, company, LinkedIn URL); for a COMPANY search, a company. LoneScale documents no schema for it, so nothing below this key is declared.	object	—

{
  "id": "c_9f3a1b2c",
  "payload": {
    "company_name": "Analytical Engines",
    "current_position": "VP Engineering",
    "domain": "analyticalengines.com",
    "first_name": "Ada",
    "full_name": "Ada Lovelace",
    "id": "c_9f3a1b2c",
    "last_name": "Lovelace",
    "linkedin_url": "https://www.linkedin.com/in/ada-lovelace/",
    "location": "London, United Kingdom",
    "workflow_id": "wf_7d21"
  },
  "workflow_id": "wf_7d21"
}

Notes

LoneScale sends no signature and offers no shared secret, so a delivery cannot be authenticated. Treat the payload as untrusted input and keep the callback URL out of anything public.
One run per record, idempotent on LoneScale's own record id where the body carries one, and on a digest of the record otherwise — so an identical redelivery does not start a second run.
The hook is removed at LoneScale when the workflow is unpublished, disabled or archived.
LoneScale's documentation domain no longer resolves; every path this trigger uses is taken from the integration LoneScale maintains in n8n.

Related LoneScale nodes

See Event run in a workflow.

In a technical demo we add the LoneScale connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.

Book a technical demo Talk to sales