n8n on its own
- A Gmail, Outlook or iCloud address looks just like a work email
- Throwaway inboxes restart free trials again and again
- You keep your own list of free email domains, and it goes stale
- Typos like [email protected] become lost leads and bounces
n8n + isBusinessEmail()
- Every address gets a category: business, personal, disposable, relay, education
- Disposable and relay inboxes are caught, including new services on known mail servers
- Lists and DNS checks are maintained for you, behind one HTTP call
- did_you_mean suggests a fix for typos, and you see whether the company runs Google Workspace or Microsoft 365
Try it from your terminal
Before you set up n8n, see what the API returns. Test addresses need no key; for real addresses use a free key. Full reference.
# Test addresses need no key
curl -sG https://api.isbusinessemail.com/v1/check \
--data-urlencode "[email protected]"curl -s https://api.isbusinessemail.com/v1/check \
-H "Authorization: Bearer $IBE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"email":"[email protected]","policy":"b2b"}'{
"email": "[email protected]",
"is_business": false,
"category": "personal",
"recommendation": "block",
"policy": "b2b",
"is_free_provider": true,
"is_disposable": false,
"did_you_mean": null,
"workspace": {
"google_workspace": { "detected": false },
"microsoft_365": { "detected": false }
}
}There are two ways to call the API from n8n: the isBusinessEmail community node, or n8n’s built-in HTTP Request node. Either way, it’s one call per item, then you route on recommendation or category.
The isBusinessEmail node
- Settings → Community nodes → Install, enter
n8n-nodes-isbusinessemail. - Add the isBusinessEmail node and create an isBusinessEmail API credential with your secret key (
ibe_live_…). - Pick an operation:
- Check: an email address, domain or website URL, with optional policy, deep check and workspace lookup.
- Verify Mailbox: checks that the mailbox exists, without sending an email.
- Get Usage: your plan limits and how much of your quota you’ve used.
The node returns the same fields as the API, so the routing and error handling below apply unchanged. It can also be a tool for n8n’s AI Agent. Source: github.com/tillforty/n8n-nodes-isbusinessemail.
On n8n Cloud, community nodes are only available once n8n has verified them. Until then, use the HTTP Request node.
With the HTTP Request node
1. Create a credential
Credentials → New → Header Auth
| Field | Value |
|---|---|
| Name | Authorization |
| Value | Bearer ibe_live_… |
2. Add an HTTP Request node
| Setting | Value |
|---|---|
| Method | POST |
| URL | https://api.isbusinessemail.com/v1/check |
| Authentication | Generic Credential Type → Header Auth → the credential above |
| Send Body | On, Body Content Type JSON |
| Specify Body | Using JSON |
| JSON (switch the field to Expression) | { "email": "{{ $json.email }}" } |
| Options → Timeout | 3000 |
Adjust $json.email to wherever the address is in your incoming data (a form trigger, a webhook, a CRM node).
The node outputs the full response: category, recommendation, reasons, workspace…
Route the result
Add a Switch node with rules on {{ $json.recommendation }}:
| Output | Rule | Typical next step |
|---|---|---|
| allow | equals allow |
Create the CRM contact, notify sales |
| review | equals review |
Add to a review list or Slack channel |
| block | equals block |
Drop, or send a “please use your work email” reply |
Want Microsoft 365 companies routed to a specific rep? Add an IF node on {{ $json.workspace.microsoft_365.detected }}.
Don’t let errors stop the workflow
In the node’s Settings (the isBusinessEmail node or HTTP Request):
- Retry On Fail: on, 2 tries, wait 1000 ms (handles
429and brief network issues). - On Error: Continue (using error output), and route the error output to your “allow” branch, so leads aren’t lost if the call fails.
Many items at once
Both nodes run once per item, and each call counts toward your quota (100 a day on a new free account; paid plans count per month). For large imports, either:
- add Loop Over Items with a small batch size and a Wait node to stay within per-second limits, or
- aggregate up to 100 addresses and call
POST /v1/check/batchwith{ "items": [...] }, then splitresultsback into items.
Test it
Use [email protected], [email protected] and [email protected]. They return fixed results and don’t count (full list).
Official docs: n8n documentation (HTTP Request node). See also: B2B lead qualification.