Skip to content
Notis

Turn useful Notion contact comments into Apollo enrichment

When a comment adds a name, email, or profile link, use Apollo to make the contact details easier to review.

Trigger

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.

Action

Apollo People Enrichment

Enrich one person with verified contact and profile data — email, profile, and optionally a mobile phone number — from an email, name, LinkedIn URL, or Apollo id.

Why this helps

Good leads often appear in discussion, then disappear beneath newer comments before anyone completes the research.

  • Give contact mentions a concrete next research step.
  • Reduce the need to reopen comment threads and search manually.
  • Help preserve useful prospect context from team discussion.

Setup

Build it in a few focused steps.

  • 1Connect Notion and Apollo to Notis once through the portal.
  • 2Create an automation in the portal or ask Notis to enrich a person in Apollo when a new Notion comment contains contact details.
  • 3Select the Notion Comment Created trigger.
  • 4Choose where Notis should report runs and test with one real comment containing a contact identity.

Questions about this workflow

Can comments anywhere in the workspace trigger it?

Comment Created can fire for any new comment the integration can access, or it can be scoped to a page.

Is there a Notion setup requirement?

The Notion integration needs the Read comments capability. If it was authorized before that capability was enabled, re-authorize the connection.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

Notion triggers

Apollo actions

Recurring trigger

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

TriggerScheduled

Apollo People Enrichment

Enrich one person with verified contact and profile data — email, profile, and optionally a mobile phone number — from an email, name, LinkedIn URL, or Apollo id.

ActionInstant

Webhook trigger

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

TriggerInstant

Apollo Organization Job Postings

Retrieve a company's active job postings by its Apollo organization id.

ActionInstant

All Page Events

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

TriggerPolling

Apollo Get Complete Organization Info

Get the complete record for a company by its Apollo organization id.

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

Apollo Organization Search

Find companies by headcount, location, revenue, funding, keywords, and technology.

ActionInstant

New Comment

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

TriggerPolling

Apollo News Articles Search

Search news articles about companies by organization, category, and date.

ActionInstant

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

Apollo Get Complete Person Info

Get the complete record for a person by their Apollo person id.

ActionInstant

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 Apollo, 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 Apollo.