Add latitude to an updated IP record
If your review needs a latitude coordinate, let a property update cue Ipdata to retrieve that one detail from the associated IP.
Trigger
Page Properties Updated
Triggers when properties of a Notion page are updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.
Action
IPData: Latitude
Tool to return only the latitude for an IP. Use when only the latitude coordinate is needed.
Why this helps
Remembering to collect a coordinate after editing a record can create a low-priority task that lingers.
- Retrieve only the latitude coordinate.
- Tie a coordinate lookup to an existing record update.
- Reduce the chance of leaving the detail for later.
Setup
Build it in a few focused steps.
- 1Connect Notion and Ipdata co to Notis once through the portal.
- 2Create an automation with one plain-language instruction to retrieve the latitude for the record's IP after a change.
- 3Choose Notion Page Properties Updated and select a channel for run reports.
- 4Test with one updated record containing a real IP.
Questions about this workflow
Does it return longitude too?
This action returns latitude only. Ipdata has a separate action for longitude.
Can it be scoped to a database?
Yes. Select the relevant data source when choosing the Notion properties trigger.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Ipdata co. A trigger fires from one place; an action lands in another.
Notion 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.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
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.
Comment Created
Triggers when a new comment is created in Notion. Optional `page_id` filter scopes to comments on a specific page. When omitted, fires for any new comment in the workspace the integration has access to. Requires the 'Read comments' capability on the Notion integration. If a connection was authorized before that capability was enabled, the user must re-authorize the connection for comment events to flow.
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.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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.
Database Created
Triggers when a new Notion database (the container) is created. A database is the post-2025-09-03 container that holds one or more data sources. This trigger fires for the container's creation event (`database.created`), distinct from `NOTION_DATASOURCE_CREATED` which fires when a new data source is added to an existing database. Most customers calling Notion's `POST /v1/databases` (the legacy API) or creating a database via the Notion UI will see this event. Adding a new data source to an existing database fires `data_source.created` instead — use `NOTION_DATASOURCE_CREATED` for that. Notion's payload puts `entity.type: "block"` (the container is a `child_database` block in the content tree) and `entity.id` is the database id.
Get City from IP
Tool to return only city for an IP. Use when only the city name is required.
Data Source Created
Triggers when a new Notion data source is created. Fires workspace-wide. The payload's `data.parent` carries the data source's tree parent (typically the teamspace) for downstream filtering. A single template-based database creation can fire multiple `data_source.created` events at once — one per data source the template instantiates.
IPData: Continent Code
Tool to return only continent_code for an IP. Use when only the continent code is required.
Data Source Schema Updated
Triggers when a Notion data source's schema is updated. Fires on column add / remove / rename. Payload includes `data.updated_properties: [{id, name, action}]` so consumers can discriminate the kind of change downstream. Optional `data_source_id` filter scopes to schema changes on a single data source. When omitted, fires for any schema change in the workspace the integration has access to. Note: adding a column also fires `page.properties_updated` once per existing row in the data source. Customers wanting a single structural-change signal should use this trigger.
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.
Notion 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.