Turn a Notion update into a lightweight sales pulse
When a Notion page changes, Notis can retrieve new Leadoku connections and share a compact sales context pulse.
Trigger
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Action
Get New Connections
Retrieves a list of new connections from growth-x (formerly leadoku). the 'tsfield' for this action is 'connection date' (mapped from 'creation date' in the api response).
Why this helps
Sales context may be spread across notes and conversations, and switching tools to spot new connections can feel like one more task.
- Get a timely reminder that new connections may be worth reviewing.
- Keep sales context in view during regular Notion work.
- Reduce the chance that relationship research is forgotten.
Setup
Build it in a few focused steps.
- 1Connect Notion and Leadoku to Notis once in the portal.
- 2Create an automation in the portal or ask Notis conversationally.
- 3Give Notis one instruction to retrieve new Leadoku connections after a relevant Notion page change and summarize the result briefly.
- 4Select All Page Events and choose where run reports should arrive.
- 5Test with one real page update and refine the instruction if needed.
Questions about this workflow
Will every workspace page change run it?
All Page Events covers page creation and updates across the workspace the integration can access. Describe the relevant sales context in your instruction.
Can it take sales actions?
No. This workflow retrieves new connections and reports context.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Leadoku. A trigger fires from one place; an action lands in another.
Notion triggers
Leadoku actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get New Connections
Retrieves a list of new connections from growth-x (formerly leadoku). the 'tsfield' for this action is 'connection date' (mapped from 'creation date' in the api response).
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
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 Leadoku, 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 Leadoku.