Actions8
- Contact Actions
- Company Actions
- Prospecting Actions
Overview
This node integrates with the Lusha API to enrich company data in bulk. It accepts an array of company objects, each identified by a unique ID and specified by either domain, company name, or fully qualified domain name (FQDN). The node sends this batch to Lusha's bulk company enrichment endpoint and returns detailed enriched information for each company.
Common scenarios where this node is beneficial include:
- Enhancing CRM records with additional company details such as industry, size, revenue, and contact information.
- Performing bulk data enrichment before marketing campaigns to improve targeting accuracy.
- Automating data quality improvements by appending verified company attributes in large datasets.
Practical example:
You have a list of 50 companies identified by their domains and names. You want to enrich these records with up-to-date company profiles including employee count, industry classification, and contact emails. This node allows you to send all 50 companies in one request and receive enriched data for each.
Properties
| Name | Meaning |
|---|---|
| Companies JSON | An array of company objects to enrich (maximum 100). Each object must have a unique id and at least one of: domain, name, or fqdn. Example: [{"id": "1", "domain": "example.com"}, {"id": "2", "name": "Acme Corporation"}] |
Output
The output is a JSON array where each item corresponds to an enriched company object returned from the Lusha API. Each object contains detailed company information as provided by Lusha, such as company profile data, contact details, and other enrichment fields.
The node does not output binary data.
Dependencies
- Requires an active Lusha API key credential configured in n8n.
- Makes HTTP POST requests to the Lusha bulk company enrichment endpoint (
https://api.lusha.com/bulk/company). - The node expects the input JSON to be valid and properly formatted.
Troubleshooting
- Invalid JSON in Companies field: If the input JSON string for companies is malformed, the node will throw an error indicating invalid JSON. Ensure the JSON syntax is correct.
- Maximum 100 companies allowed per request: The node enforces a limit of 100 companies per bulk request. Sending more than 100 will cause an error. Split your input into batches of 100 or fewer.
- Missing required fields: Each company object must have a unique
idand at least one identifier (domain,name, orfqdn). Omitting these will likely result in API errors or incomplete results. - API authentication errors: Ensure that the Lusha API key credential is correctly set up and has sufficient permissions.
- Network or API errors: Standard HTTP errors may occur due to connectivity issues or API limits. Review error messages and retry as needed.
Links and References
- Lusha API Documentation
- Lusha Bulk Company Enrichment Endpoint (refer to official docs for request/response schema)