Skip to content
Notis

Enrich new Notion prospects automatically

Give each new prospect a useful first-pass enrichment as soon as it lands in Notion.

Trigger

New Page

Triggers when a new page is added to a Notion database.

Action

/v1/enrich

Why this helps

Researching every new lead before deciding whether it deserves follow-up creates a long queue of half-finished tabs.

  • Reduce time spent opening profiles and company pages one by one.
  • Bring useful context into the prospect review process sooner.
  • Keep new leads moving instead of letting them sit untouched.

Setup

Build it in a few focused steps.

  • 1Connect Notion and api.kadec0.xyz to Notis once in the portal.
  • 2Ask Notis to create an automation that enriches each new prospect record and summarizes the useful findings.
  • 3Select the Notion New Page trigger for the relevant prospect database.
  • 4Choose where Notis should report runs, then test with one real prospect page.

Questions about this workflow

Does this run for every new Notion page?

Choose the New Page trigger for the prospect database so the automation focuses on new records there.

Do I need to configure fields?

No. Describe the enrichment outcome in the automation prompt, and Notis interprets the connected tools.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

Notion triggers

api.kadec0.xyz actions

Recurring trigger

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

TriggerScheduled

/v1/youtube

ActionInstant

Webhook trigger

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

TriggerInstant

/v1/serp-batch

ActionInstant

All Page Events

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

TriggerPolling

/v1/scrape

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

/v1/enrich

ActionInstant

New Comment

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

TriggerPolling

/v1/serp-read

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

/v1/cve

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 api.kadec0.xyz, 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 api.kadec0.xyz.