Understand local timing for campaign traffic
When a campaign visit needs time-zone context, let Notis retrieve the visitor IP's timezone details.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
IPData Time Zone for IP
Tool to return timezone data for a specific IP. Use when you need timezone details, including name, abbreviation, offset, DST status, and local current time for an IP.
Why this helps
Guessing the right local time for follow-up can add uncertainty and delay.
- Get timezone name, abbreviation, offset, DST status, and local current time.
- Use location-derived time context to plan human follow-up.
- Skip manual timezone conversion for selected visits.
Setup
Build it in a few focused steps.
- 1Connect WoopSocial and Ipdata co to Notis once in the portal.
- 2Create an automation or ask Notis for timezone details on campaign visitor IPs.
- 3Write one instruction to retrieve timezone information for IPs your backend sends when local timing matters.
- 4Choose an incoming webhook trigger and a channel for run reports.
- 5Test with one real visitor IP and review the returned timezone details.
Questions about this workflow
Does the result prove the visitor's exact local time?
It provides timezone details derived from the IP lookup. Treat it as a useful estimate rather than a verified identity or precise location.
Can I use this for every campaign visit?
You can choose which IPs your backend sends, such as visits that need time-sensitive follow-up.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link WoopSocial to Ipdata co. A trigger fires from one place; an action lands in another.
WoopSocial triggers
Ipdata co actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Advanced ASN Lookup
Tool to perform advanced ASN lookup returning prefixes, peers, and registry details. Use after confirming ASN number when detailed ASN info is required.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Carrier Data for an IP
Tool to return mobile carrier data for a specific IP. Use when you need carrier name, MCC, and MNC for an IP address.
EU-specific IP lookup
Tool to lookup a specific IP address via the EU-only data residency endpoint. Use when you need IP lookup processed and stored within the EU.
IPData: Calling Code
Tool to fetch the international calling_code for an IP's country. Use when you need only the calling code field from ipdata_co.
IPDATA Field Carrier
Tool to return only the carrier object for the calling IP. Use when you need mobile carrier details of a specific IP.
Get City from IP
Tool to return only city for an IP. Use when only the city name is required.
IPData: Continent Code
Tool to return only continent_code for an IP. Use when only the continent code is required.
Get Continent Name from IP
Tool to return only continent name for an IP. Use when only the continent name is required.
Connect any two apps with Notis in the middle.
WoopSocial and Ipdata co, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Ipdata co.