Overview
This node integrates with the Wiza API to enrich contact information by finding verified phone numbers based on various input data. It is particularly useful for sales, marketing, or recruitment professionals who need to obtain direct mobile or dial phone numbers of contacts using partial information such as email, LinkedIn URL, full name, and company details.
Typical use cases include:
- Enriching a lead list with direct phone numbers to improve outreach success.
- Verifying and supplementing existing contact records with accurate phone data.
- Automating contact enrichment workflows in CRMs or marketing automation platforms.
For example, given a contact's email or LinkedIn profile URL, the node can retrieve their verified mobile and direct dial phone numbers, helping users connect more effectively.
Properties
| Name | Meaning |
|---|---|
| Operation | The action to perform; here it is "Phone Finder" to find phone numbers for contacts. |
| Input Type | The type of input provided to identify the contact: - LinkedIn URL - Contact Details (name + company/domain) - All Fields (multiple pieces combined) |
| The contact's email address (used if Input Type is "Email" or "All Fields"). | |
| LinkedIn URL | The contact's LinkedIn profile URL (used if Input Type is "LinkedIn URL" or "All Fields"). |
| Full Name | The full name of the contact (used if Input Type is "Contact Details" or "All Fields"). |
| Company / Domain | The company name or domain where the contact works (used if Input Type is "Contact Details" or "All Fields"). |
| Additional Fields | Collection of optional parameters: - Email Type: Preferred email type to find ("Work", "Personal", "Any") - Timeout (Seconds): Maximum time to wait for enrichment completion (default 300 seconds) |
Output
The node outputs an array of JSON objects, each representing the enriched contact data returned from the Wiza API. The main output field json contains detailed contact information including phone numbers and other enrichment data.
If the enrichment process completes successfully, the output JSON includes fields such as:
id: Unique identifier of the enrichment request.is_complete: Boolean indicating if enrichment finished.- Contact details including phone numbers (mobile, direct dial), emails, job title, company, location, etc., depending on what Wiza returns.
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 Wiza service.
- The node uses HTTP POST to initiate enrichment and HTTP GET to poll for results until completion or timeout.
Troubleshooting
- Timeouts: If enrichment takes longer than the specified timeout (default 300 seconds), the node throws a timeout error. Increase the timeout property if needed.
- Failed Enrichment: If the Wiza API responds with a failure status, the node throws an error with the message returned by the API. Check input data validity and API quota.
- Invalid Response Format: If the response from Wiza does not contain expected data, an error is thrown. This may indicate API changes or network issues.
- 404 Errors During Polling: These are handled internally by retrying, but persistent 404 errors may indicate invalid enrichment IDs or expired requests.
- Missing Required Inputs: Ensure that the input fields match the selected Input Type; missing required fields will cause the API call to fail.
Links and References
- Wiza API Documentation (for detailed API usage and parameters)
- n8n Documentation (for general node usage and credential setup)