IP Blacklist Lookup API + Intercom Integration

Why connect them

The IP Blacklist Lookup API in Intercom.

Intercom connects businesses with customers through messaging. Integrating APIs with Intercom enables intelligent lead qualification, automated data enrichment, and context-aware conversations. Give your team the data they need instantly.

What you can build

Workflows worth wiring.

Validate visitor email addresses before starting conversations

Enrich lead profiles with company data from business APIs

Score conversations based on external data signals

Automatically tag users based on their domain or company type

Templates

Ready-made ideas.

New conversation started in Intercom Fetch IP blacklist lookup for user IP → add isIPBlacklisted and threatLevel as conversation note

IP Blacklist Check in Intercom

Give support agents IP threat context by showing blacklist status and threat level in Intercom conversations.

New user identified in Intercom Fetch IP blacklist lookup → if isIPBlacklisted, tag user with threatLevel for fraud-aware support

Tag High-Risk Intercom Users

Tag Intercom users connecting from blacklisted IPs so support agents can handle them with appropriate caution.

Setup

Connect it in a few steps.

Set up with Zapier

1
Set the trigger. Create a Zap with Intercom as the trigger app and "New conversation" 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 Intercom action for "Create user" 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 Intercom module set to "New conversation". 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 Intercom module for "Create user". 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 Intercom trigger node for "New conversation" 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 Intercom node for "Create user" 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 payload

What Intercom receives.

ipAddress"185.220.101.1"

isIPBlacklistedtrue

inboundfound, description

outbound—

threatLevel"high"

ipDetailsip, country, region, timezone, city, coordinates, countryName, regionName, postalCode, continent, continentName, accuracyRadius

IP Blacklist Lookup API + Intercom