Start meeting prep when you create the Notion page
Create the meeting page, then let Notis gather a sourced company brief for your upcoming conversation.
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
Research a company
Get a sourced brief before a call.
Why this helps
Meeting preparation often gets squeezed into the minutes before a call, when context is hardest to gather.
- Get a head start on company context as soon as the page exists.
- Avoid a separate research session just to prepare for the call.
- Keep preparation near your meeting notes.
Setup
Build it in a few focused steps.
- 1Connect Notion and Deep research to Notis once in the portal.
- 2Create an automation or ask Notis to research the company named in each new meeting page and prepare a sourced brief.
- 3Select the Notion Page Created trigger, scoped to your meeting parent page if appropriate.
- 4Pick a run-report channel and test using a real upcoming meeting page.
Questions about this workflow
Will this run for every new page?
It depends on the trigger scope you choose. Page Created can be scoped to new subpages under a specified parent page.
What if the meeting page lacks company details?
Include the company name or relevant context in the page so Notis has a clear subject for the research request.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Deep research. A trigger fires from one place; an action lands in another.
Notion triggers
Deep research actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Research a company
Get a sourced brief before a call.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Compare options
Weigh several products, vendors, or approaches.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Deliver it later
The report arrives as a follow-up message when it is ready.
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 Deep research, 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 Deep research.