IP Blacklist Lookup API + Zendesk Integration

Why connect them

The IP Blacklist Lookup API in Zendesk.

Zendesk is the leading customer service platform. Connecting APIs to Zendesk enables intelligent ticket routing, customer data enrichment, and automated response suggestions. Deliver better support with contextual information.

What you can build

Workflows worth wiring.

Enrich tickets with customer data from external CRM APIs

Validate customer contact information before responses

Auto-categorize tickets based on content analysis APIs

Look up order status from e-commerce APIs for customer inquiries

Templates

Ready-made ideas.

New ticket created in Zendesk Fetch IP blacklist lookup for requester IP → add isIPBlacklisted and threatLevel as internal note

IP Blacklist Check on Zendesk Tickets

Enrich Zendesk tickets with IP blacklist status so agents can identify potentially malicious requesters.

New ticket created in Zendesk Fetch IP blacklist lookup → if isIPBlacklisted, escalate ticket and add inbound.description as note

Threat-Based Zendesk Ticket Routing

Automatically escalate Zendesk tickets from blacklisted IPs and add blocklist details for the security team.

Setup

Connect it in a few steps.

Set up with Zapier

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