Lusha

Lusha API integration for contact and company enrichment

Actions8

Overview

This node integrates with the Lusha API to enrich contact data by retrieving detailed information about a single contact based on various search criteria. It is useful for enhancing existing contact records with additional data such as emails, phone numbers, job titles, and company details. Typical use cases include sales prospecting, lead enrichment, and CRM data augmentation.

For example, you can input a contact's first name, last name, and company domain to fetch enriched contact details, or provide an email address or LinkedIn profile URL to get comprehensive contact information.

Properties

Name Meaning
Search By Method to search for the contact:
- Name and Company
- Email
- LinkedIn URL
First Name Contact's first name (used when searching by Name and Company)
Last Name Contact's last name (used when searching by Name and Company)
Company Name Name of the company where the contact works (used when searching by Name and Company)
Company Domain Domain of the company (e.g., example.com) (used when searching by Name and Company)
Email Contact's email address (used when searching by Email)
LinkedIn URL Contact's LinkedIn profile URL (used when searching by LinkedIn URL)
Filter By Type of data to return:
- All Data
- Emails Only
- Phones Only

Output

The output JSON contains the enriched contact data returned from the Lusha API. This typically includes:

  • Contact personal details (name, job title, location)
  • Contact emails and phone numbers (filtered according to the "Filter By" property)
  • Company information related to the contact
  • Additional metadata provided by Lusha about the contact

No binary data is output by this node.

Dependencies

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

Troubleshooting

  • Invalid JSON in Contacts field: If providing JSON input (for bulk operations), ensure it is valid JSON format.
  • Maximum 100 contacts allowed per request: Bulk enrichment limits the number of contacts to 100.
  • Request ID is required: For some operations (not relevant here but seen in code), a request ID must be provided.
  • No contact IDs found for enrichment: When selecting contacts for enrichment, ensure that contact IDs are correctly specified or available.
  • API Key errors: Ensure the API key credential is valid and has proper permissions.
  • Network or API errors may occur; check connectivity and API status.

Links and References

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

Discussion