Skip to content
Notis

Refresh WHOIS context from page edits

When your notes change, bring the domain facts back into view so the next decision starts with current context.

Trigger

Page Content Updated

Triggers when the body content of a Notion page is 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 page content edit in the workspace the integration has access to. Notion aggregates content edits within a short window (~60s typical).

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

Research notes can drift from a domain's current WHOIS details, leaving you to remember when they were last checked.

  • Use page edits as a prompt to revisit domain facts.
  • Bring registrar and expiration context into your work session.
  • Avoid relying only on remembered lookup dates.

Setup

Build it in a few focused steps.

  • 1Connect Notion and Ip2whois to Notis once in the portal.
  • 2Create an automation in the portal or ask Notis conversationally.
  • 3In one plain-language prompt, ask Notis to look up the domain on the edited Notion page and summarize current WHOIS details.
  • 4Pick Page Content Updated and scope it to the domain page or data source; choose a channel for run reports.
  • 5Test by editing one real domain page that contains a domain name.

Questions about this workflow

Can this watch a specific domain page?

Yes. The Page Content Updated trigger can be scoped to a page or data source.

What if the page does not contain a domain?

Describe in the prompt how Notis should handle pages with no usable domain, such as reporting that no lookup was performed.

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.

TriggerScheduled

IP2WHOIS Domain Lookup

Tool to retrieve WHOIS information for a domain. Use when you need registrar and contact details for a specific domain.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Hosted Domains Lookup

Tool to retrieve hosted domains for a given IP address. Use this after validating the IP.

ActionInstant

All Page Events

Triggers when any Notion page is created or updated across the workspace.

TriggerPolling

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.

TriggerInstant

New Comment

Triggers when a new comment is added to a specified Notion block or page.

TriggerPolling

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.

TriggerInstant

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.

TriggerInstant

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.

TriggerInstant

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.