Enrich leads and optimize contact timing with IPGeolocation webhooks
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.
What this workflow does
This workflow has 8 nodes and runs when an HTTP POST request hits its webhook URL. Along the way it connects Ipgeolocation (community).
How it runs
Trigger: When an HTTP POST request hits its webhook URL.
- Check IP Address Validity (Code): runs custom JavaScript code
- Validate IP Syntax (If): checks a condition and branches into true / false
- Fetch IP Geolocation Data (Ipgeolocation): uses Ipgeolocation
- Error Response for Invalid IP (Respond to Webhook): sends the response back to the webhook caller
- Fetch Timezone Details (Ipgeolocation): get timezone
- Assemble Lead Profile (Code): runs custom JavaScript code
- Reply with Lead Details (Respond to Webhook): sends the response back to the webhook caller
Services it uses
Before you upgrade to n8n 3.0
We can't fully verify this one: it relies on 1 community package, and n8n 3.0 turns unverified community packages off by default (N8N_UNVERIFIED_PACKAGES_ENABLED=false).
- Check that n8n-nodes-ipgeolocation is verified or supports 3.0 (used in Fetch IP Geolocation Data, Fetch Timezone Details).
Nodes used (5)
- Webhook
n8n-nodes-base.webhook - Ipgeolocation
n8n-nodes-ipgeolocation.ipgeolocation - Code
n8n-nodes-base.code - Respond to Webhook
n8n-nodes-base.respondToWebhook - If
n8n-nodes-base.if
From the author
Quick overview This webhook-based workflow accepts a lead payload with an IP address, enriches it using IPGeolocation.io ipgeolocation and timezone lookups, and returns a structured profile that includes location, network organization, and a recommendation to…