Enrichment → Start Enrichment
AI-generatedOverview
The FullEnrich node initiates a bulk enrichment request to enhance contact data with additional information. It is useful for scenarios where users want to enrich contact details such as emails, phone numbers, company information, and professional network URLs in bulk. For example, a marketing team could use this node to enrich their contact list with updated emails and phone numbers before launching a campaign.
Use Case Examples
- Enriching a list of contacts with updated work and personal emails and phone numbers.
- Starting an enrichment task with a unique name and receiving results via a webhook URL.
Properties
| Name | Meaning |
|---|---|
| Enrichment Name | A unique name for this enrichment task, used to identify the enrichment process. |
| Webhook URL | The webhook URL to receive results of the enrichment. Must be publicly accessible, such as an n8n webhook trigger URL. |
| Per-Contact Webhook URL | URL called when each individual contact finishes enrichment, used for receiving contact-specific enrichment events. |
| Company Domain | The domain of the company related to the contacts being enriched. |
| Company Name | The name of the company related to the contacts being enriched. |
| First Name | The first name of the contact to enrich. |
| Last Name | The last name of the contact to enrich. |
| Professional Network URL | The LinkedIn or other professional network URL of the contact. |
| Custom Fields | Additional custom key-value pairs to include in the enrichment request. |
| Fields to Enrich | Specifies which contact fields should be enriched, such as emails and phones. The available options depend on the node version: version 1 supports 'Contact Emails' and 'Contact Phones'; version 2 supports 'Work Emails', 'Personal Emails', and 'Contact Phones'. |
Output
JSON
enrichmentId- The unique identifier of the enrichment task started.status- The current status of the enrichment request.results- The enrichment results returned from the service, typically including enriched contact data.
Dependencies
- An API key credential for FullEnrich service authentication
Troubleshooting
- Ensure the webhook URLs are publicly accessible to receive enrichment results; otherwise, the node will not receive callbacks.
- Verify that the enrichmentName is unique to avoid conflicts or overwriting existing enrichment tasks.
- Check that the API key credential is valid and has sufficient permissions to start enrichment requests.
- If the node throws errors related to missing required fields, ensure all mandatory properties like enrichmentName and enrichFields are provided.