Give fraud review more IP context
When a record moves into your review queue, let Notis retrieve IP location details and include them in the run report.
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
Bulk IP Geolocation
Tool to retrieve geolocation information for multiple IP addresses in bulk. Use when processing up to 1000 IPs at once.
Why this helps
Switching from a review queue to a separate IP lookup adds friction exactly when a quick, consistent check matters.
- Attach geographic context to records as review properties change.
- Help reviewers avoid a separate manual lookup step.
- Make the check easy to repeat across the review queue.
Setup
Build it in a few focused steps.
- 1Connect Notion and Ip2location io to Notis once in the portal.
- 2Create an automation in the portal or ask Notis in a connected channel.
- 3Describe the outcome in one instruction: when a Notion review record's properties are updated and it includes an IP address, look up the IP location and report the record reference and result.
- 4Pick Page Properties Updated for the relevant data source, then choose where Notis should report runs.
- 5Test by updating one real review record that has an IP address.
Questions about this workflow
Does an IP location result decide whether a record is fraudulent?
No. This workflow retrieves geolocation information for human review; it does not establish fraud or make a risk decision.
Can I limit the workflow to a review database?
Choose Page Properties Updated and scope the trigger to the relevant data source.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Ip2location io. A trigger fires from one place; an action lands in another.
Notion triggers
Ip2location io actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Bulk IP Geolocation
Tool to retrieve geolocation information for multiple IP addresses in bulk. Use when processing up to 1000 IPs at once.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Domain WHOIS Lookup
Tool to retrieve WHOIS information for a given domain. Use when you need domain registration and contact details via IP2WHOIS API.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get API Key
Tool to retrieve the configured API key. Use when authentication is needed for IP2Location.io requests.
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.
IP2WHOIS Hosted Domain
Tool to retrieve hosted domain names by IP address. Use when you need to list domains hosted on a given IP. Call after confirming the IP.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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.
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.
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 Ip2location 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 Ip2location io.