// crm
Via APIZoho CRM email verification with pingutil
Zoho CRM leads pile up from web forms, imports and integrations, and bad addresses only surface when a campaign or a rep's email bounces. A workflow rule on lead creation runs a Deluge function that calls pingutil with invokeurl, then writes the verification status, email category and company industry to lead fields with zoho.crm.v8.updateRecord.
Where it connects: Workflow rule on Leads (on create) with an associated Deluge function (Automation category) that uses invokeurl and zoho.crm.v8.updateRecord
What goes wrong without it
- Our Zoho Campaigns sends keep bouncing on leads that came in through the website form.
- Lead assignment rules treat a hotmail.com lead the same as one from a 500-person company.
- Reps fill in Industry by hand, so half the leads never get one.
What you can do with Zoho CRM and pingutil
Verify leads at creation
The function writes `status` and `reason` to custom fields. A second workflow rule or a custom view can keep `invalid` leads out of campaigns and cadences.
Qualify by email type
Write `category` to the lead. Assignment rules can route `company` leads to sales and `free` or `isp` leads to a nurture owner.
Fill company fields
For `company` domains, copy `company.industry` and `company.employee_size_estimate` to custom fields so scoring rules have data from the first minute.
Set it up
- 1
Create custom Lead fields: Email Status, Email Reason, Email Category, Company Industry and Company Size (single-line text keeps it simple), and note their API names.
- 2
Store your pingutil key in an org variable (Setup, Developer Hub, Variables) so it is not hard-coded.
- 3
In Setup, Developer Hub, Functions, create a function in the Automation category with arguments `leadId` and `email`, and paste the code below.
- 4
Create a workflow rule on Leads that runs on create, and under Instant Actions associate the function, mapping `leadId` to Lead Id and `email` to Email.
- 5
Create a test lead and check the function's Logs tab in Developer Hub if fields stay empty.
void automation.pingutil_check_lead(String leadId, String email)
{
if(email == null || email == "")
{
return;
}
headers = Map();
headers.put("Authorization","Bearer " + zoho.crm.getOrgVariable("pingutil_api_key"));
headers.put("Content-Type","application/json");
update = Map();
// 1. Mailbox check
vBody = Map();
vBody.put("email",email);
v = invokeurl
[
url :"https://pingutil.com/v1/verify"
type :POST
parameters:vBody.toString()
headers:headers
];
if(v.get("status") != null)
{
update.put("Email_Status",v.get("status"));
update.put("Email_Reason",v.get("reason"));
}
// 2. Category and company profile
lBody = Map();
lBody.put("input",email);
l = invokeurl
[
url :"https://pingutil.com/v1/lookup"
type :POST
parameters:lBody.toString()
headers:headers
];
if(l.get("category") != null)
{
update.put("Email_Category",l.get("category"));
company = l.get("company");
if(company != null)
{
update.put("Company_Industry",company.get("industry"));
update.put("Company_Size",company.get("employee_size_estimate"));
}
}
// Errors (429 quota_exceeded, 5xx) come back without status/category: write nothing, the lead stays as it was.
if(!update.isEmpty())
{
zoho.crm.v8.updateRecord("Leads",leadId.toLong(),update);
}
}What to do with each result
| pingutil result | Action in Zoho CRM |
|---|---|
| `status: "invalid"` | Exclude from Zoho Campaigns lists and set Lead Status to Junk Lead or your equivalent. |
| `status: "risky"`, `reason: "accept_all"` | Keep, but send at low volume; catch-all domains cannot be confirmed. |
| `status: "unknown"` | Re-check later with a scheduled function; not a verdict. |
| `category: "free"` or `"isp"` | Assign to a nurture owner instead of the sales queue. |
| `company.industry` | Write to Company Industry and use it in scoring rules. |
Limits to plan for
- Zoho CRM functions are limited to 5,000 Deluge statements per call, and each updateRecord call counts as an API call against your Zoho limits.
- Verification of a slow mail server can take up to about 25 seconds. Workflow functions run in the background, so the lead saves immediately and fields fill shortly after.
- pingutil allows 300 verified addresses a day (3,000 a month) per account; leads created after the budget is spent stay unverified until a scheduled re-check picks them up. Those are Free plan limits; Enterprise has custom limits.
Zoho CRM documentation
- www.zoho.com/crm/developer/docs/functions/getting-started/quickstart/build-automation.html
- www.zoho.com/deluge/help/webhook/invokeurl-api-task.html
- www.zoho.com/deluge/help/crm/update-record-V8.html
Zoho CRM is a trademark of its owner. This integration uses Zoho CRM's documented extension points; it is not an official Zoho CRM app.
Common questions
- Do I need code for this in Zoho CRM?
- A short Deluge function, yes. Zoho's workflow webhook action can send lead fields to a URL, but writing the result back to the lead needs either a function or a service that calls the Zoho CRM API.
- Will updating the lead trigger the workflow again?
- Not if the rule runs on create only. If you also trigger on edit, add a condition such as Email Status is empty so the function's own update does not re-run it.
Stop bad addresses in Zoho CRM today
Sign in with your email, create an API key and paste it into the step above. Test on a few real addresses first: the live demo shows exactly what your Zoho CRM setup will receive.