Refresh IP context when inventory structure changes
Keep an evolving inventory useful by refreshing its address context when the structure changes.
Trigger
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.
Action
Batch IP Lookup
Tool to perform batch IP lookups. Use when grouping up to 1,000 IPs or URL patterns into a single POST request.
Why this helps
Schema changes can signal a review cycle, but refreshing the address context manually is easy to postpone.
- Use one structural-change signal to prompt an inventory review.
- Process multiple IPs together with Ipinfo io batch lookup.
- Avoid repeating lookups one record at a time.
Setup
Build it in a few focused steps.
- 1Connect Notion and Ipinfo io to Notis once in the portal.
- 2Create an automation in the portal or ask Notis to create it through conversation.
- 3In one instruction, ask Notis to review IPs in the specified inventory data source after a schema change and use Ipinfo io batch IP lookup for the addresses found.
- 4Choose the Notion Data Source Schema Updated trigger for that data source and a channel for run reports.
- 5Test with a schema change and an inventory containing real IPs.
Questions about this workflow
Why use a schema change as the trigger?
It provides a structural-change signal when inventory fields are added, removed, or renamed.
How many lookups can one batch contain?
The supplied Ipinfo io batch IP lookup event supports up to 1,000 IPs or URL patterns in a POST request.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Ipinfo io. A trigger fires from one place; an action lands in another.
Notion triggers
Ipinfo io actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Batch Lite Lookup
Tool to perform bulk Lite IP lookups. Use when you need to group up to 1000 IP or URL pattern lookups into a single request.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Batch IP Lookup
Tool to perform batch IP lookups. Use when grouping up to 1,000 IPs or URL patterns into a single POST request.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Abuse Contact
Tool to retrieve abuse contact information for a specific IP address. Use when you need organizational abuse details of an IP.
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.
Get IP Carrier Info
Tool to get carrier information for a given IP address. Use when you need mobile carrier details.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Company Info for an IP
Tool to retrieve company info for a specific IP. Use when you need organization details behind an 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 IP Information
Tool to retrieve detailed information about an IP address. Use when you need geolocation, ASN, and network flags for a specific IP or 'me'.
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.
Get IP Privacy Details
Tool to retrieve privacy-related flags (VPN, proxy, Tor, relay, hosting) for an IP address. Use when you need to detect anonymizing usage after confirming an IP.
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.
Connect any two apps with Notis in the middle.
Notion and Ipinfo io, 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 Ipinfo io.