Add a domain check to new project subpages
When a project page appears under your domain hub, bring its domain facts into the work before they get lost in setup.
Trigger
Page Added to Page
Fires when a new subpage (a `child_page` type block) is added under a specified parent Notion page.
Action
IP2WHOIS Domain Lookup
Tool to retrieve WHOIS information for a domain. Use when you need registrar and contact details for a specific domain.
Why this helps
New project pages can create scattered follow-up if domain checks depend on someone remembering to start them.
- Attach a repeatable research step to a chosen project hub.
- Reduce the chance that a domain check slips during setup.
- Keep a concise lookup summary available for planning.
Setup
Build it in a few focused steps.
- 1Connect Notion and Ip2whois to Notis once in the portal.
- 2Create the automation in the portal or tell Notis the desired result in plain language.
- 3Ask Notis to find a domain on each new project subpage under the chosen hub and summarize its WHOIS details.
- 4Choose Page Added to Page, set the project hub as its parent, and select a run-report channel.
- 5Test by adding a child page with one real domain.
Questions about this workflow
Does the trigger watch all workspace pages?
No. Page Added to Page is designed for new subpages under the specified parent page.
Can it check a domain mentioned in the page title?
Describe where Notis should look for the domain, including the page title or content, in the prompt.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Ip2whois. A trigger fires from one place; an action lands in another.
Notion triggers
Ip2whois actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
IP2WHOIS Domain Lookup
Tool to retrieve WHOIS information for a domain. Use when you need registrar and contact details for a specific domain.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Hosted Domains Lookup
Tool to retrieve hosted domains for a given IP address. Use this after validating the IP.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
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.
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 Ip2whois, 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 Ip2whois.