Zapier can call any HTTP API with Webhooks by Zapier. Add it after your trigger (a new form submission, a new CRM contact, a new Stripe customer), then use Filter or Paths on the result. Webhooks by Zapier availability depends on your Zapier plan.
1. Add the request step
Action: Webhooks by Zapier → Custom Request
| Field | Value |
|---|---|
| Method | POST |
| URL | https://api.isbusinessemail.com/v1/check |
| Data | {"email": "<map the email field from your trigger>"} |
| Headers | Authorization = Bearer ibe_live_… and Content-Type = application/json |
Test the step. Zapier parses the JSON response, so fields such as Category, Recommendation, Is Business and the nested Workspace … Microsoft 365 … Detected become mappable in later steps (Zapier flattens nested keys into readable labels).
2. Act on it
Only continue for work emails: add Filter by Zapier with Recommendation → (Text) Exactly matches → allow.
Different handling per verdict: use Paths by Zapier:
| Path | Condition | Example action |
|---|---|---|
| Work email | Recommendation = allow |
Create a deal, notify the account executive in Slack |
| Needs a look | Recommendation = review |
Add a row to a review sheet |
| Personal/disposable | Recommendation = block |
Add to a nurture list instead of sales |
Route by tenant: add a path on Workspace Microsoft 365 Detected = true to send Microsoft shops to the rep who handles your Microsoft integration.
3. Write the verdict back
Map Category, Recommendation and, if useful, Workspace Microsoft 365 Tenant Id into custom fields in your CRM. Your team can then filter and report on them without another call.
Tips
- Every Zap run is one check toward your daily quota. Put a Filter before the request step if the trigger includes records you don’t need to check.
- For bulk back-fills, a script with the batch endpoint is faster and cheaper than replaying a Zap.
- Test with the test addresses; they never count.
Official docs: Zapier Help Center (Webhooks by Zapier, Filter, Paths). See also: Sales routing by workspace.