LoneScale Trigger

Triggers when a LoneScale workflow produces prospect intelligence results

Overview

Receives webhook notifications from LoneScale when a LoneScale workflow completes and produces results. LoneScale is a sales intelligence platform that monitors prospect signals such as job changes, hiring intent, technology adoption, and funding events. The user selects which LoneScale workflow to listen to, and when that workflow runs and generates output, LoneScale sends the results to this webhook. The raw payload is forwarded as-is with no transformation. Useful for triggering outreach sequences, updating CRM records, enriching lead data, and alerting sales teams when key buying signals are detected.

Category: Sales
Tool Name: lonescale_trigger
Version: 1

Appearance: Icon: lucide-Target | Color: #6366f1

Node Type

Trigger — webhook (receives incoming HTTP callbacks)

Input / Output

Direction	Port(s)
Input	None (trigger node)
Output	Output

Credentials

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

Parameters

Parameter	Type	Required	Default	Description
Workflow	string	Yes	—	The ID of the LoneScale workflow to listen for results from. Enter the workflow ID directly; the LoneScale API lists your workflows at GET /workflows.

Output Data

Each delivery produces one output item. LoneScale’s result payload is placed directly on the item alongside three metadata fields:

{
  "_trigger": "lonescale_webhook",
  "_timestamp": "2026-01-01T00:00:00.000Z",
  "_webhookEvent": "workflow_result",
  "workflow_id": "wf-abc123",
  "first_name": "Jane",
  "last_name": "Doe",
  "email": "jane.doe@example.com",
  "company_name": "Acme Corp",
  "current_position": "VP of Sales",
  "linkedin_url": "https://linkedin.com/in/janedoe",
  "domain": "acme.com",
  "signal": "job_change",
  "signal_details": "Recently promoted to VP of Sales"
}

• _trigger — always lonescale_webhook.
• _timestamp — ISO 8601 timestamp of when the delivery arrived.
• _webhookEvent — always workflow_result.

Every other field comes from LoneScale untouched, so the exact shape depends on what the selected LoneScale workflow produces — typically prospect identity (first_name, last_name, email, linkedin_url), company context (company_name, domain, current_position) and the detected signal (signal, signal_details). Inspect one real delivery before writing downstream expressions, then reference values as {{ $json.email }} or {{ $json.signal }}.

Usage Examples

• Start a workflow when LoneScale detects a job change for a tracked prospect
• Trigger an outreach sequence when LoneScale identifies a new hiring signal
• Update CRM records when LoneScale enriches a contact with new data
• Alert the sales team when LoneScale detects a funding event at a target account

Example Configuration

Listen to one LoneScale workflow:

{
  "type": "lonescale_trigger",
  "parameters": {
    "workflow": "wf-abc123"
  }
}

Listen to a second LoneScale workflow in a separate flow:

{
  "type": "lonescale_trigger",
  "parameters": {
    "workflow": "wf-hiring-signals"
  }
}

Trigger Behavior

• Activation: When the workflow is activated, a webhook endpoint is registered with the service.
• Deactivation: The webhook is automatically unregistered when the workflow is deactivated.
• Payload: The incoming webhook payload is parsed and output as workflow items.
• Verification: Supports signature verification where applicable.

Tips

Entry point that fires when a LoneScale workflow produces results. Select which LoneScale workflow to monitor by entering its ID. When that workflow runs and generates output, LoneScale sends the results to this webhook. The raw payload is forwarded as-is, containing whatever data the LoneScale workflow produces (prospect details, signals, enrichment data, etc.).