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 daily 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.