Add a domain check to campaign intake
Bring registration context into campaign planning as soon as a domain is added to Notion.
Trigger
Page Created
Triggers when a new Notion page is created. Customer optionally scopes with at most one of: - data_source_id: new row in this data source - parent_page_id: new sub-page under this page (immediate parent only) With neither set, fires for any new page in the workspace the integration has access to. Notion sends ~60s aggregation latency on most events.
Action
Domain WHOIS Lookup
Tool to retrieve WHOIS information for a given domain. Use when you need domain registration and contact details via IP2WHOIS API.
Why this helps
Campaign planning can stall when domain research sits in a separate task someone must remember to start.
- Make domain research part of the campaign intake rhythm.
- Give planners registration context near the new domain record.
- Reduce manual research follow-up.
Setup
Build it in a few focused steps.
- 1Connect Notion and Ip2location io once in the portal.
- 2Create an automation in Automations or ask Notis to make it conversationally.
- 3Use one instruction: when a new campaign domain page is created, retrieve WHOIS information for its domain and report the details with the page reference.
- 4Choose Page Created scoped to the campaign domain data source, then select a report channel.
- 5Test with one real campaign domain page.
Questions about this workflow
What should the Notion page contain?
It should contain the domain Notis should look up.
Does the lookup register or change the domain?
No. The action retrieves WHOIS information; it does not modify domain registration.
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.