LoneScale

CRM & salesAPI keyConnection test available

LoneScale job-change and hiring-intent signals — build PEOPLE and COMPANY lists, waterfall-enrich a contact for email, phone or a refreshed profile, flag whether they changed company, and source people at an account by persona (API key in X-API-KEY).

OCNORA ships 7 typed LoneScale operations and 1 trigger. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run. Endpoints not covered by a typed node are called at https://public-api.lonescale.com through the HTTP node with the same credential.

Before you connect LoneScale

Authentication
API key
Credential
the LoneScale API key, or {"api_key": "…"}the API key, or {"api_key": "…"}
Connection test
Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.
Prerequisites
  • 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.

Prerequisites are taken from the connection notes in this provider’s node contracts; each node’s reference page says which apply to it.

What you can do with LoneScale

Operations, grouped by what they do to your data, plus 1 trigger that start a run.

A sample LoneScale workflow

  1. 1
    Eventtrigger.lonescale_event
    Start a run when a LoneScale search finds a person or company (job change, hiring intent).
  2. 2
    List Listslonescale.list_lists
    Read the lists on the account, optionally only one kind of list.
  3. 3
    Add List Itemlonescale.add_list_item
    Add one person or company to an existing LoneScale list.

An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.

LoneScale questions

How does OCNORA authenticate with LoneScale?
With a stored API key credential, shaped the LoneScale API key, or {"api_key": "…"} or the API key, or {"api_key": "…"}. A connection test can check it when you add it.
What can I automate with LoneScale?
7 typed operations and 1 trigger, each with a reference page listing its config fields and the shapes it emits.
What if the LoneScale operation I need is not listed?
Call https://public-api.lonescale.com from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
Are there templates that use LoneScale?
Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
How are LoneScale calls controlled?
Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.

See your first LoneScale workflow run.

Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.