Lusha

Lusha API integration for contact and company enrichment

Actions8

Overview

The "Search Contacts" operation in the Prospecting resource allows users to search for contacts using a wide range of filters related to both the contacts themselves and their associated companies. This node is useful for sales, marketing, or recruitment professionals who want to find targeted contact lists based on job titles, departments, seniority, location, company size, industry, technologies used, and more.

Typical use cases include:

  • Building targeted lead lists by filtering contacts with specific job titles or seniority levels within certain industries or geographic locations.
  • Finding contacts working at companies of a particular size or revenue range.
  • Narrowing down prospects by filtering contacts that have specific data points like phone numbers or work emails.
  • Combining multiple filters to create highly customized prospecting queries.

For example, a user could search for all contacts with the title "VP Sales" or higher seniority, located in the United States, working at companies with 1001-5000 employees in the Technology industry.

Properties

Name Meaning
Page Page number of results to retrieve (starts at 0).
Page Size Number of results per page, between 10 and 40.
Contact Filters Collection of filters applied to contacts:
- Job Titles: Comma-separated list of job titles (e.g., CEO, CTO).
- Departments: Select one or more departments (e.g., Sales, Marketing).
- Seniority: Select seniority levels from Founder to Intern.
- Countries: Select countries where contacts are located.
- States: Comma-separated states.
- Cities: Comma-separated cities.
- Existing Data Points: Filter contacts that have phone, work email, mobile phone, or direct phone.
Company Filters Collection of filters applied to companies associated with contacts:
- Company Names: Comma-separated company names.
- Domains: Comma-separated company domains.
- Employee Count: Select employee count ranges (e.g., 1-10, 10001+).
- Industries: Select main industries (e.g., Finance, Healthcare).
- Revenue Min/Max: Minimum and maximum revenue thresholds.
- Sub Industries: Select sub-industries (e.g., Software Development, Fintech).
- Company Countries: Headquarters countries.
- SIC Codes: Comma-separated SIC codes.
- NAICS Codes: Comma-separated NAICS codes.
- Technologies: Comma-separated technologies used by companies (e.g., Salesforce, AWS).
- Intent Topics: Comma-separated intent topics (e.g., Digital Transformation).

Output

The output JSON contains the search results with detailed information about contacts matching the specified filters. The response includes:

  • data: An array of contact objects returned by the API.
  • Pagination metadata such as:
    • totalResults: Total number of matching contacts.
    • pageLength: Number of contacts per page.
    • totalPages: Calculated total pages available.
    • currentPage: Current page index.
    • isFirstPage / isLastPage: Booleans indicating if the current page is the first or last.
  • Arrays of contact IDs for convenience:
    • allContactIds: All contact IDs returned in the current result set.
    • visibleContactIds: Contact IDs marked as shown.
    • newContactIds: Contact IDs not previously shown.

This structured output enables further processing, such as enriching selected contacts or exporting the data.

Dependencies

  • Requires an API key credential for authentication with the external Lusha API service.
  • The node makes HTTP requests to Lusha's endpoints, specifically to https://api.lusha.com/prospecting/contact/search.
  • Proper configuration of the API key credential in n8n is necessary for successful execution.

Troubleshooting

  • Missing or invalid API key: The node requires a valid API key credential. Ensure the API key is correctly configured in n8n credentials.
  • Invalid filter values: Providing malformed or unsupported filter values (e.g., incorrect JSON format or invalid option selections) may cause errors. Validate inputs before running.
  • Empty results: If no contacts match the filters, the output will contain empty data arrays. Try broadening filters or checking filter criteria.
  • Pagination issues: Requesting pages beyond the available range may return empty results. Use pagination metadata (totalPages) to control page requests.
  • API rate limits: Excessive requests might be throttled by the external API. Implement error handling and retries as needed.

Common error messages:

  • "Request ID is required": Not applicable for this operation but appears in enrichment operations; ensure correct parameters.
  • "No contact IDs found for enrichment": Also related to enrichment, not search.
  • JSON parsing errors: Occur if JSON input fields are malformed.

Links and References

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

Discussion