n8n’s HTTP Request node is all you need: one call per item, then route on recommendation or category. Works on n8n Cloud and self-hosted.
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…
3. 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 }}.
4. Don’t let errors stop the workflow
In the HTTP Request node’s Settings:
- 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
The HTTP Request node runs once per item, and each call counts toward your daily quota (100 a day on a new account). 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 workspace@test.isbusinessemail.com, personal@test.isbusinessemail.com and disposable@test.isbusinessemail.com. They return fixed results and don’t count (full list).
Official docs: n8n documentation (HTTP Request node). See also: B2B lead qualification.