Overview
This node initiates a bulk enrichment request to a FullEnrich service, which enriches contact data based on provided input fields. It is designed to send multiple contact records in one request and receive enriched data asynchronously via a webhook URL.
Typical use cases include:
- Enhancing lead or contact information with additional details such as emails or phone numbers.
- Automating data enrichment workflows where updated contact info is required for marketing, sales, or CRM systems.
- Integrating with external enrichment services to keep contact databases up-to-date.
For example, you can provide a list of contacts with names and company domains, specify which fields to enrich (e.g., emails and phones), and set a webhook URL to receive the enriched results once processing completes.
Properties
| Name | Meaning |
|---|---|
| Enrichment Name | A unique name identifying this enrichment task. |
| Webhook URL | The publicly accessible URL where enrichment results will be sent asynchronously (e.g., an n8n webhook trigger URL). |
| Company Domain | The domain of the company associated with the contact. |
| Company Name | The name of the company associated with the contact. |
| First Name | The first name of the contact person. |
| Last Name | The last name of the contact person. |
| LinkedIn URL | The LinkedIn profile URL of the contact person. |
| Custom Fields | Additional key-value pairs to include custom data fields for enrichment. |
| Fields to Enrich | Specifies which fields should be enriched. Options: Contact Emails, Contact Phones. |
Output
The node outputs JSON objects for each input item indicating whether the enrichment request was successfully sent. Each output item contains:
success: Boolean indicating if the request was accepted.sent: The original data sent for enrichment (including names, company info, LinkedIn URL, custom fields, and requested enrich fields).webhook_url: The webhook URL where results will be delivered.
The node does not directly output the enriched data; instead, it relies on the configured webhook URL to receive asynchronous enrichment results.
Dependencies
- Requires an API key credential for authenticating with the FullEnrich service.
- Needs a publicly accessible webhook URL to receive enrichment results asynchronously.
- Uses HTTP POST requests to the FullEnrich API endpoint
/contact/enrich/bulk.
Troubleshooting
Common issues and error messages:
- Invalid LinkedIn URL: If the LinkedIn URL format is incorrect, the node throws an error indicating "Invalid LinkedIn URL provided".
- Webhook URL errors: Errors like "Invalid or missing webhook URL" indicate the webhook URL is either malformed or inaccessible.
- Custom field limits exceeded: Errors about custom key or value length exceeding limits mean the custom fields are too long.
- Missing required fields: Errors such as "First name is required", "Last name is required", or "Company domain is required" indicate mandatory inputs are missing.
- Authentication failures: HTTP 401 errors suggest invalid or missing API credentials.
- Bad Request (HTTP 400): Usually means input data is invalid or incomplete.
- Server errors (HTTP 500): Indicate issues on the FullEnrich service side; retry later.
To resolve these:
- Verify all required fields are correctly filled.
- Ensure the webhook URL is publicly accessible and correctly formatted.
- Check API credentials are valid and properly configured.
- Keep custom field keys and values within allowed character limits.
Links and References
- FullEnrich API Documentation (hypothetical link)
- n8n Webhook Trigger Node documentation for setting up webhook URLs
- General best practices for data enrichment and API authentication