LoneScale icon

LoneScale

Enrich contacts and source contacts from companies with LoneScale

Search Company

AI-generated

Overview

This node operation allows users to search for a company using various identifiers such as company domain, LinkedIn ID, LinkedIn slug, or company name. It queries the LoneScale API to retrieve company information based on the provided input parameters. Optionally, it can enrich the company data with additional details like headcount breakdown if no cached match is found.

Use Case Examples

  1. A user wants to find detailed information about a company by providing its website domain (e.g., stripe.com).
  2. A user has a LinkedIn company ID or slug and wants to retrieve company details from LoneScale.
  3. A user prefers to search by company name for a best-effort match when other identifiers are not available.

Properties

Name Meaning
Company Domain The domain of the company to look up, e.g., stripe.com. Used as a primary identifier for the company search.
LinkedIn ID The numeric LinkedIn company ID extracted from the linkedin.com/company/ URL. Used as an identifier for the company search.
Slug The LinkedIn universal name or slug, which is the trailing segment in linkedin.com/company/{slug}. Used as an identifier for the company search.
Company Name The name of the company to search for. This is a best-effort match and is less deterministic than domain, LinkedIn ID, or slug.
Enrich A boolean flag indicating whether to fall back to on-demand enrichment when no cached match is found, and to attach a headcount breakdown when possible.

Output

JSON

  • json - The company data returned from the LoneScale API search results.

Dependencies

  • LoneScale API key credential for authentication

Troubleshooting

  • Ensure at least one of the identifiers (domain, LinkedIn ID, slug, or name) is provided; otherwise, the search may return no results or an error.
  • If the API returns no results, verify the correctness of the input parameters and try enabling the 'Enrich' option to allow fallback enrichment.
  • Handle API errors gracefully by enabling 'Continue On Fail' in the node settings to avoid workflow interruption.

Discussion