Overview
This node integrates with the Wiza API to enrich contact information by finding verified emails, phone numbers, or LinkedIn profile details. It supports three main operations:
- Email Finder: Finds verified work and personal email addresses using a contact's name, company info, or LinkedIn URL.
- Phone Finder: Finds mobile and direct dial phone numbers using similar inputs.
- LinkedIn Profile Finder: Retrieves a contact’s LinkedIn profile URL and key details like job title, company, and location.
The node is useful for sales, recruiting, marketing, or any scenario where enriching contact data is needed to improve outreach or CRM records. For example, you can input a contact’s full name and company domain to find their verified email and phone number, or provide an email address to get their LinkedIn profile details.
Properties
| Name | Meaning |
|---|---|
| Operation | The type of enrichment to perform: Email Finder, Phone Finder, or LinkedIn Profile Finder. |
| Input Type | The method used to identify the contact: Email, LinkedIn URL, Contact Details (name + company/domain), or All Fields (multiple pieces of info). |
| The contact’s email address (used when Input Type is "email" or "allFields"). | |
| LinkedIn URL | The contact’s LinkedIn profile URL (used when Input Type is "linkedinUrl" or "allFields"). |
| Full Name | The full name of the contact (used when Input Type is "contactDetails" or "allFields"). |
| Company / Domain | The company name or domain where the contact works (used when Input Type is "contactDetails" or "allFields"). |
| Additional Fields - Email Type | Preferred email type to find: Work, Personal, or Any. |
| Additional Fields - Timeout (Seconds) | Maximum time in seconds to wait for the enrichment process to complete (default 300 seconds). |
Output
The node outputs a JSON object containing the enriched contact data returned from the Wiza API. This includes fields such as:
- Verified email addresses
- Phone numbers (if applicable)
- LinkedIn profile URL and related profile details (job title, company, location)
- Enrichment status and metadata
The output corresponds directly to the API response under the data property and reflects the completed enrichment result.
No binary data output is produced by this node.
Dependencies
- Requires access to the Wiza API endpoint at
https://wiza.co/api/individual_reveals. - Needs an API authentication token configured in n8n credentials (referred generically as an API key credential).
- Network connectivity to the Wiza service.
- The node uses HTTP POST to initiate enrichment and polls via GET requests until completion or timeout.
Troubleshooting
- Timeouts: If enrichment takes longer than the specified timeout (default 300 seconds), the node will throw a timeout error. Increase the timeout if necessary.
- Invalid Inputs: Providing incomplete or incorrect contact details may cause the enrichment to fail or return no results.
- API Errors: Errors from the Wiza API (e.g., invalid API key, rate limits, or internal errors) will be surfaced as node operation errors. Check your API credentials and usage limits.
- 404 Not Found during polling: The node handles intermittent 404 responses while polling for enrichment status by retrying, but persistent 404s indicate the enrichment ID is invalid or expired.
- Failed Enrichment: If the API returns a failure status, the node throws an error with the provided message.
Links and References
- Wiza API Documentation (for detailed API capabilities and parameters)
- n8n Documentation (for general node usage and credential setup)