Lusha

Lusha API integration for contact and company enrichment

Overview

The "Contact - Enrich Bulk" operation in this node allows users to enrich multiple contact records simultaneously by sending an array of contact objects (up to 100) to the Lusha API. Each contact must have a unique identifier and at least one of these identifiers: LinkedIn URL, full name with company information, or email address. The node then returns enriched data for each contact, which can include emails, phone numbers, or all available data depending on the selected filter.

This operation is beneficial when you have a batch of contacts and want to enhance their profiles with additional information such as verified emails, phone numbers, job titles, or company details. For example, sales teams can use it to bulk update their CRM contacts with accurate contact info, or marketing teams can enrich lead lists before campaigns.

Properties

Name Meaning
Contacts JSON A JSON array of contact objects to enrich (maximum 100). Each object requires a unique contactId and either a LinkedIn URL, full name + company, or email. Example: [{"contactId": "1", "fullName": "John Doe", "companies": [{"name": "Acme Corp", "isCurrent": true}]}]
Filter By Specifies the type of data to return for each contact:
• All Data (default)
• Emails Only
• Phones Only

Output

  • The output is an array where each item corresponds to an enriched contact.
  • Each item contains a json field with the enriched contact data returned from the Lusha API.
  • The structure of each enriched contact includes various fields such as emails, phone numbers, names, companies, and other contact details depending on the API response and the selected filter.
  • No binary data is output by this operation.

Dependencies

  • Requires an API key credential for the Lusha API.
  • The node makes HTTP requests to the Lusha API endpoints:
    • POST https://api.lusha.com/v2/person for bulk enrichment.
  • Proper configuration of the Lusha API key in n8n credentials is necessary.

Troubleshooting

  • Invalid JSON in Contacts field: If the input JSON for contacts is malformed, the node will throw an error indicating invalid JSON. Ensure the JSON syntax is correct.
  • Maximum 100 contacts allowed per request: Sending more than 100 contacts will cause an error. Limit the batch size accordingly.
  • Missing required identifiers: Each contact must have a unique contactId and at least one identifier (LinkedIn URL, full name + company, or email). Missing these will likely result in incomplete or failed enrichment.
  • API authentication errors: If the API key is missing or invalid, the node will fail to authenticate. Verify that the API key credential is correctly set up.
  • Empty or no results: If no matching data is found for the provided contacts, the output may be empty or contain minimal data.

Links and References


This summary focuses exclusively on the "Contact" resource with the "Enrich Bulk" operation as requested.

Discussion