Give new runbooks a quick view of available event sources
When an analytics runbook page is created, prompt a Keen collection list so the documentation can start with an understanding of available data.
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
Inspect All Event Collections
Tool to retrieve schema info for all event collections. Use when you need to list collection names and optional property schema for a given project. Use include_schema to toggle schema details.
Why this helps
Runbooks can begin without an easy view of available event sources, leading to extra discovery work later.
- Bring event source discovery into runbook creation.
- Make available collection names easy to review while documenting.
- Reduce later context switching for documentation authors.
Setup
Build it in a few focused steps.
- 1Connect Notion and Keen io to Notis once in the portal.
- 2Create an automation in Automations or ask Notis conversationally.
- 3Write one instruction asking Notis to list Keen event collections when an analytics runbook page is created.
- 4Select the Notion Page Created trigger and choose a channel for run reports.
- 5Create a real runbook page and review the collection inventory.
Questions about this workflow
Will this write the inventory into the runbook?
No. It retrieves the inventory in the automation run; the instruction can ask Notis to summarize it there if supported by your connected workflow.
Can this run for all new pages?
The trigger can be scoped to the relevant parent page or data source.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Keen io. A trigger fires from one place; an action lands in another.
Notion triggers
Keen io actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Inspect All Event Collections
Tool to retrieve schema info for all event collections. Use when you need to list collection names and optional property schema for a given project. Use include_schema to toggle schema details.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Inspect Collection Property
Tool to return details for a specific property in an event collection. Use when you need to inspect a property's inferred type and resource URL.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Inspect Single Event Collection
Tool to retrieve schema info for a single event collection. Use when you need the inferred property types for a specific collection in a project.
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.
List Cached Dataset Definitions
Tool to list cached dataset definitions for a project. Use when you need to page through dataset definitions.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Select Unique
Tool to return unique values for a target property. Use when distinct property values are required for matching events with optional filters and timeframe constraints.
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.
Unrevoke Access Key
Tool to unrevoke (reactivate) a specific access key. Use when needing to restore a previously revoked API key.
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 Keen 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 Keen io.