Make 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
Make + 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 Make, 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 }
}
}In Make (formerly Integromat), the HTTP → Make a request module calls the API, and a Router with filters sends each verdict down its own route.
1. Configure the HTTP module
| Field | Value |
|---|---|
| URL | https://api.isbusinessemail.com/v1/check |
| Method | POST |
| Headers | Authorization: Bearer ibe_live_… |
| Body type | Raw |
| Content type | JSON (application/json) |
| Request content | {"email": "{{1.email}}"} (map the email from your trigger module) |
| Parse response | Yes |
| Timeout | 5 |
Run the module once so Make learns the response structure; afterwards data.category, data.recommendation, data.workspace.microsoft_365.detected and the rest are mappable.
2. Add a Router
| Route | Filter | Example |
|---|---|---|
| Work email | data.recommendation equal to allow |
Create a CRM deal, notify sales |
| Review | data.recommendation equal to review |
Add to a Google Sheet for manual review |
| Blocked | data.recommendation equal to block |
Add to a nurture sequence |
Add a fourth route with data.workspace.microsoft_365.detected equal to true to tag Microsoft 365 companies, or use the tenant ID in later steps.
3. Handle errors
Right-click the HTTP module → Add error handler → Resume, and supply a fallback output with recommendation = allow. If the API times out or you hit a limit, the lead still flows through instead of stopping the scenario.
Tips
- Each run uses one check from your quota and one Make operation per module. Filter out records you don’t need before the HTTP module.
- For large lists, aggregate up to 100 emails into an array and call
/v1/check/batchwith{"items": [...]}, then iterate overdata.results. - Test with test addresses: no key needed, never counted.
Official docs: Make Help Center (HTTP app, Router, error handling). See also: CRM hygiene.