Why connect themThe IP Blacklist Lookup API in Microsoft Outlook.
Microsoft Outlook powers enterprise email worldwide. Connecting APIs to Outlook enables automated email processing, intelligent categorization, and seamless data extraction. Enhance your enterprise email workflows with external intelligence.
What you can buildWorkflows worth wiring.
Validate sender addresses to identify potential phishing attempts
Extract and process data from structured email formats
Auto-categorize emails based on content analysis
Enrich calendar events with location and weather data
TemplatesReady-made ideas.
Scheduled daily trigger Fetch IP blacklist lookup for monitored IPs → send Outlook email with ipAddress, isIPBlacklisted, and threatLevelIP Blacklist Report via Outlook
Receive a daily Outlook report with blacklist check results for your critical IP addresses.
New security event detected Fetch IP blacklist lookup → if isIPBlacklisted, send Outlook alert with threatLevel and inbound.descriptionBlacklist Alert via Outlook
Get an Outlook email alert when security events involve blacklisted IPs with threat context.
SetupConnect it in a few steps.
Set up with Zapier
- 1
Set the trigger. Create a Zap with Microsoft Outlook as the trigger app and "New email" as the event. Connect your account.
- 2
Add the API action. Add APIVerve as the action, select the IP Blacklist Lookup API, and map your trigger data to the request.
- 3
Send it back. Add a second Microsoft Outlook action for "Send email" and map the returned fields (like ipAddress) into it.
- 4
Test & turn on. Test the Zap with real data to confirm the mapping, then turn it on.
Set up with Make
- 1
Add the trigger. Create a scenario and add a Microsoft Outlook module set to "New email". Authenticate your account.
- 2
Call the API. Add an HTTP module pointing at api.apiverve.com/v1/ipblacklistlookup with your x-api-key header. Pass the trigger's data as the input.
- 3
Parse & map. Add a JSON module to read the response, then a Microsoft Outlook module for "Send email". Map fields like data.ipAddress into place.
- 4
Activate. Run once to confirm the mapping, then switch the scenario on and set its schedule.
Set up with n8n
- 1
Add the trigger node. Start a workflow with a Microsoft Outlook trigger node for "New email" and connect your credentials.
- 2
Add an HTTP Request node. Point it at api.apiverve.com/v1/ipblacklistlookup using Header Auth (x-api-key). Feed in the trigger data.
- 3
Map with expressions. Add a Microsoft Outlook node for "Send email" and reference the response with expressions such as {{ $json.data.ipAddress }}.
- 4
Execute & activate. Execute manually to verify, then activate the workflow for production.
The payloadWhat Microsoft Outlook receives.
ipAddress"185.220.101.1"
isIPBlacklistedtrue
inboundfound, description
outbound—
threatLevel"high"
ipDetailsip, country, region, timezone, city, coordinates, countryName, regionName, postalCode, continent, continentName, accuracyRadius
