There could be a few reasons why the Wiza Work Email waterfall is showing "Error" without specific details:
1. API credits may have run out, causing validation errors.
2. The email found by Wiza might have failed the validation check, prompting the waterfall to continue running.
To resolve this:
1. Check if you need to purchase additional credits for your email verification provider.
2. If credits are available, try re-running the waterfall for rows with errors.
If the issue persists, you may need to request human assistance for a more detailed investigation. Click on "Talk to a person" for further help.
Hello Mick! Thank you for reaching out! š
I took a look at the Wiza step that was throwing the āError running integration: Error. There was an error when trying to pull this email address.ā message. In logs, I saw Wizaās response: LBKS{ "status": { "code": 400, "message": "Please provide either a profile URL, an email, or a full name and company." } }LBKSThe request sent included your leadās full name but only their web domain: LBKS{ "full_name": "Ernesto Haro", "domain": "[1haro1hvac.us](http://1haro1hvac.us)" }LBKSWiza requires either a profile URL / known email, or a full name and a company string (e.g., āHaro HVACā). Since it didnāt receive the company name, it returned the 400 error you saw.
Iāve gone ahead and saved the correct Company Name column in the Wiza fieldāmapping settings, so future runs will send both full_name and company.
You shouldnāt see this error again, but let me know if anything else pops up and Iāll jump right on it! š
.png){kind=logo}
