Leadspicker Node icon

Leadspicker Node

Interact with Leadspicker API
Join our community

Actions14

Overview

This node interacts with the Leadspicker API to automatically find and retrieve contact persons associated with a company based on its LinkedIn URL or handle. It is particularly useful for sales, recruiting, or marketing professionals who want to quickly gather relevant contacts from a target company’s LinkedIn presence without manual searching.

The "By Company Linkedin" operation under the AutoCPH resource allows users to specify job functions (e.g., CEO, Founder, Head of Sales) to filter contacts, limit the number of results returned, and optionally enrich the contacts with email addresses. Additional options enable live verification of current employment status and use of semantic similarity techniques to better match job functions.

Practical examples:

  • A recruiter wants to find all current Heads of Engineering at a company by providing the company’s LinkedIn page.
  • A sales team member seeks to identify decision-makers like CEOs or Founders at a prospect company and get their emails if available.
  • Marketing professionals want to build targeted lists of contacts filtered by specific roles within companies identified by their LinkedIn handles.

Properties

Name Meaning
Company Linkedin URL or Handle (companyLinkedin) The LinkedIn URL or handle of the company to search contacts for. This identifies the target company on LinkedIn.
Functions (functions) Job functions to filter contacts by. Users can add multiple job functions such as "CEO", "Founder", or "Head of Sales" to narrow down the search to relevant roles.
Search Result Limit (searchResultLimit) The maximum number of person contacts to return in the search results. Must be at least 1. Default is 2.
Enrich with Emails (enrichEmails) Boolean flag indicating whether to attempt to find and include email addresses for the returned contacts. Defaults to false.
Additional Options (additionalOptions) Collection of optional settings:
- Live Check Current Position: Whether to verify live if the person currently works at the company (default true).
- Use Embeddings Similarity: Use semantic similarity to compare provided functions with persons' positions (default true).
- Embeddings Distance Threshold: Numeric threshold controlling how close the semantic match must be (default 0.53; lower means closer match).

Output

The node outputs an array of JSON objects representing persons found matching the criteria. Each object typically includes details about the person such as name, position, and potentially enriched email addresses if requested.

The exact structure depends on the API response but generally contains:

  • Person identifiers and names
  • Job titles/positions
  • Company LinkedIn information
  • Email addresses (if enrichment enabled)
  • Possibly other metadata related to the contact

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Leadspicker API via an API key credential configured in n8n.
  • The node makes HTTP POST requests to Leadspicker endpoints /autocph/by-company-linkedin.
  • No additional external services are required beyond the Leadspicker API.
  • Proper API authentication credentials must be set up in n8n for the node to function.

Troubleshooting

  • Common issues:

    • Invalid or missing company LinkedIn URL/handle will cause the API request to fail or return no results.
    • If the API key credential is not configured or invalid, authentication errors will occur.
    • Setting the search result limit too high may lead to longer response times or rate limiting.
    • Providing job functions that do not match any current employees may yield empty results.

  • Error messages:

    • "The operation "byCompanyLinkedin" is not supported for AutoCPH resource." — indicates a misconfiguration or unsupported operation selection.
    • Network or authentication errors from the API will be surfaced as error messages; ensure API keys are valid and network connectivity is stable.
    • Validation errors if required parameters like companyLinkedin are missing.

  • Resolutions:

    • Double-check the LinkedIn URL or handle format.
    • Verify API credentials and permissions.
    • Adjust filters and limits to reasonable values.
    • Enable "Live Check Current Position" to avoid stale data.

Links and References

If you need further details on other operations or resources, feel free to ask!

Discussion