Lusha

Lusha API integration for contact and company enrichment

Actions8

Overview

The "Enrich Contacts" operation under the "Prospecting" resource in this node allows users to enrich contact data based on previous search results from the Lusha API. This operation is useful for enhancing contact records with additional information such as emails, phone numbers, job titles, and other professional details that were not initially available.

Typical scenarios include:

  • Enriching all contacts returned by a prior prospecting search.
  • Enriching only new contacts that have not been previously revealed.
  • Enriching only contacts that have been revealed before.
  • Enriching a custom selection of contacts specified by their IDs.

For example, after performing a contact search with filters (e.g., job title, location), you can use this operation to enrich selected contacts with detailed contact information to improve your CRM data or sales outreach efforts.

Properties

Name Meaning
Request ID The unique identifier of the prospecting search request whose results are to be enriched.
Selection Type How to select contacts for enrichment:
- All Contacts: Enrich all contacts from the search results.
- New Contacts Only: Enrich only contacts not previously shown.
- Revealed Contacts Only: Enrich only contacts that have been previously revealed.
- Custom Selection: Manually specify contact IDs to enrich.
Contact IDs Comma-separated list of contact IDs to enrich; required if Selection Type is "Custom".

Output

The output JSON contains the enriched contact data returned by the Lusha API. This typically includes detailed contact information such as names, emails, phone numbers, job titles, company affiliations, and other relevant professional data.

If multiple contacts are enriched, the output will be an array of objects, each representing one enriched contact. Each output item is paired with the corresponding input item index.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the Lusha API.
  • The node makes HTTP requests to Lusha's endpoints, specifically to:
    • https://api.lusha.com/v2/person for single or bulk enrichment.
    • https://api.lusha.com/prospecting/contact/enrich for enriching contacts from prospecting searches.
  • Proper configuration of the API key credential in n8n is necessary.

Troubleshooting

  • Missing Request ID: The operation requires a valid Request ID from a previous prospecting search. If missing, the node throws an error "Request ID is required".
  • No Contact IDs Found: If no contact IDs are found or provided for enrichment (especially when using custom selection), the node throws "No contact IDs found for enrichment".
  • Invalid Contact IDs Format: Ensure that contact IDs are provided as a comma-separated string without extra spaces or invalid characters.
  • API Errors: Errors from the Lusha API (e.g., rate limits, invalid credentials) will be propagated. Verify API key validity and usage limits.
  • Continue On Fail: If enabled, errors per item will be captured in the output JSON with error messages instead of stopping execution.

Links and References

Discussion