Skip to content
Notis

Discover domains from new company pages

Create a company page in Notion and get likely domains ready for a quick review.

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

Name to Domain Search

Tool to find company domain(s) by company name. use when you have a company name and need up to 3 likely domains.

Why this helps

A company page can sit incomplete while you switch tools to look up its website.

  • Kick off domain discovery when a company page is created.
  • Reduce the effort of moving from note-taking into research.
  • Review a short list of candidate domains before enrichment.

Setup

Build it in a few focused steps.

  • 1Connect Notion and Bigpicture io to Notis once through the portal.
  • 2Create an automation and tell Notis to search for likely company domains whenever you create a company page, using its company name.
  • 3Select the Notion Page Created trigger and choose where Notis should report runs.
  • 4Test by creating one company page with a recognizable company name.

Questions about this workflow

Can this run on pages outside a database?

Yes. The Page Created trigger can fire for new pages in the workspace the integration can access. You can scope it to a parent page if needed.

Does Bigpicture io return a single guaranteed match?

Name to Domain Search can return up to three likely domains. Confirm the correct domain before using it for detailed company data.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Notion to Bigpicture io. A trigger fires from one place; an action lands in another.

Notion triggers

Bigpicture io actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Company Find

Tool to lookup company data by domain name. use when you need detailed company profile by providing a website domain. use after confirming domain correctness.

ActionInstant

Webhook trigger

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

TriggerInstant

IP to Company Lookup

Tool to lookup company by ip address. use after obtaining an ip to get detailed company info.

ActionInstant

All Page Events

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

TriggerPolling

Name to Domain Search

Tool to find company domain(s) by company name. use when you have a company name and need up to 3 likely domains.

ActionInstant

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 Bigpicture 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 Bigpicture io.