Overview
This node integrates with the Wiza API to enrich contact information by finding verified email addresses, phone numbers, or LinkedIn profile details. It supports multiple input types such as email address, LinkedIn URL, or a combination of full name and company/domain, allowing flexible ways to identify and enrich contacts.
Common scenarios where this node is beneficial include:
- Sales and marketing teams looking to find verified work or personal emails for outreach.
- Recruiters seeking direct phone numbers or LinkedIn profiles of potential candidates.
- Data enrichment workflows that require validated contact details from partial information.
For example, given a contact's full name and company domain, the node can find their verified work email. Alternatively, providing a LinkedIn profile URL can return detailed contact info including job title and location.
Properties
| Name | Meaning |
|---|---|
| Operation | The type of enrichment to perform: Email Finder, Phone Finder, or LinkedIn Profile Finder. |
| Input Type | The method used to provide contact data: Email, LinkedIn URL, Contact Details (name + company), or All Fields (multiple inputs). |
| The contact's email address (used when Input Type is "Email" or "All Fields"). | |
| LinkedIn URL | The contact's LinkedIn profile URL (used when Input Type is "LinkedIn URL" or "All Fields"). |
| Full Name | The full name of the contact (used when Input Type is "Contact Details" or "All Fields"). |
| Company / Domain | The company name or domain where the contact works (used when Input Type is "Contact Details" or "All Fields"). |
| Additional Fields: Email Type | Preferred email type to find: Work, Personal, or Any. Default is Work. |
| Additional Fields: Timeout (Seconds) | Maximum time in seconds to wait for the enrichment process to complete. Default is 300 seconds. |
Output
The node outputs an array of JSON objects, each representing the enriched contact data returned by the Wiza API. The structure includes fields such as:
id: Unique identifier of the enrichment request.is_complete: Boolean indicating if enrichment is finished.status: Status of the enrichment process.- Various contact details depending on the operation, e.g., verified emails, phone numbers, LinkedIn profile data, job titles, company info, and location.
If the enrichment fails or times out, the node throws an error instead of outputting incomplete data.
The node does not output binary data.
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 is necessary.
- The node uses built-in n8n helper methods to handle authenticated HTTP requests.
Troubleshooting
- Timeouts: If enrichment takes longer than the specified timeout (default 300 seconds), the node will throw a timeout error. Increase the timeout value in Additional Fields if needed.
- Invalid Input: Providing insufficient or incorrect input data (e.g., missing required fields for the chosen Input Type) may cause the API to fail or return no results.
- API Errors: Errors from the Wiza API (such as rate limits, invalid API keys, or internal errors) will be surfaced as node operation errors. Verify API credentials and usage limits.
- 404 Not Found: During polling for enrichment completion, 404 responses are handled by retrying until timeout. Persistent 404 errors may indicate invalid request IDs or expired jobs.
- Failed Enrichment: If the API returns a status of "failed", the node throws an error with the provided message. Check input data accuracy and API account status.
Links and References
- Wiza API Documentation (for detailed API capabilities and parameters)
- n8n HTTP Request Node Documentation (for understanding requestWithAuthentication helper)