Resolve domain questions on a Notion page
Keep a focused domain discussion moving by bringing the relevant WHOIS details into view when a new comment arrives.
Trigger
New Comment
Triggers when a new comment is added to a specified Notion block or 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
A comment can flag an issue without giving you the ownership or expiration facts needed to resolve it.
- Focus lookups on a page where domain decisions already happen.
- Answer basic WHOIS questions with less manual searching.
- Make comment-driven follow-up easier to pick up.
Setup
Build it in a few focused steps.
- 1Connect Notion and Ip2whois to Notis once in the portal.
- 2Open Automations to create the workflow, or tell Notis what to do conversationally.
- 3Describe one outcome: look up a domain mentioned in a new comment on the selected page and summarize its registrar and expiration.
- 4Choose New Comment, specify the relevant page, and set a channel for run reports.
- 5Test by posting a comment with a real domain on that page.
Questions about this workflow
How is this different from watching all comments?
New Comment is scoped to a specified block or page, so the workflow can focus on a chosen discussion.
What if a comment discusses several domains?
Tell Notis in the prompt whether to look up each domain or ask for clarification when the comment is ambiguous.
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.