Review IP security risk for orders and signups with IPGeolocation
UnknownUnknown. This template uses community nodes we can't verify statically. Uses community nodes that can't be verified statically (unverified community packages are off by default in 3.0). Static check, last run 2026-10-19.
Community nodes
These come from third-party npm packages. In n8n 3.0 unverified community packages are off by default (N8N_UNVERIFIED_PACKAGES_ENABLED=false).
n8n-nodes-ipgeolocation(Check Security Risk)
Nodes used (5)
- Webhook
n8n-nodes-base.webhook - Code
n8n-nodes-base.code - If
n8n-nodes-base.if - Respond to Webhook
n8n-nodes-base.respondToWebhook - Ipgeolocation
n8n-nodes-ipgeolocation.ipgeolocation
What it does
Quick overview This workflow receives an order or signup event via webhook, validates the request, checks the IP address against IPGeolocation’s Security API, and returns a structured JSON risk assessment (including recommendation, severity, and signals) to help you decide whether to allow, verify, or manually review the event. How it works 1. Receives a POST webhook request containing an IP address (and optional order/signup metadata). 2. Validates the payload format (including a basic IPv4/IPv6 syntax check) and returns a 400 response with validation details if the request is invalid. 3. Calls IPGeolocation’s getIpSecurityInfo endpoint to retrieve security signals such as threat score, VPN/proxy/Tor flags, and related indicators. 4. Converts the IPGeolocation response into a workflow risk score with human-readable signals and a recommendation (allow, additional verification, or manual review). 5. Returns the full assessment as JSON to the webhook caller, or returns a 502 “lookup failed” response if the IP security lookup cannot be completed. Setup 1. Create an IPGeolocation API key and select it in the IPGeolocation node credential field. 2. Activate the workflow and copy the production webhook URL, then configure your store/app to send a POST request to it with a JSON body that includes an ip field. 3. Update your client payload mapping (optional) to include eventType, orderId/customerId, amount, currency, and source if you want them reflected in the response.