Native and near-native
- ClayHTTP API column that works today on any plan. Provider listing in review.
- HubSpotEnrich contacts on creation or on demand, write back with a state per field.
- n8nCommunity node with Lookup, Bulk, Company and Verify, or the raw HTTP node.
- ZapierLook up person action, verify action, bulk-completed trigger.
- Google Sheets=HEYENRICH(A2, "work_email") for lists under a few thousand rows.
- Anything elseOne endpoint, JSON in and out. Smartlead, Instantly, HeyReach and Salesforce via CSV or a Zapier step today.
Actions and what each costs
The same credits as everywhere else. A miss inside any integration costs nothing.
| Action | Input | Returns | Credits |
|---|---|---|---|
| Look up person | LinkedIn URL, name + domain, or work email | work_email, personal_email, mobile with state and checked_at | 1 / 2 / 5 per field found |
| Company by domain | Domain | Email pattern and share, catch-all, MX provider, headcount band | 1, or free with a person match |
| Verify email | Address | state and checked_at | 0.5 |
| Bulk job | Rows or a file | Job id, then a download URL | Same per filled field |
Rules that apply everywhere
A miss costs nothing
Inside Clay, HubSpot or a Zap, an empty field is credits_charged: 0. No special handling.
Ask for the fields you'll use
Every integration lets you choose work email, personal email, mobile or any mix. You're only charged for what comes back.
States come along
verified, risky or notfound and the check date are written wherever the value goes, so you can filter before sending.
Opt-outs flow through
A person.suppressed webhook tells your system to delete a record. HubSpot clears the mapped properties automatically.