Turn measurement comments into dataset requests
When someone spells out an analytics need in a Notion discussion, let Notis carry that context into a dataset request.
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
Create Expanded Data Set
Tool to create an expanded data set for a property. use when you need to combine specific dimensions and metrics into a custom dataset after property creation.
Why this helps
Useful measurement requirements are often buried in comment threads instead of reaching the analytics setup step.
- Brings a written request into an actionable Analytics step.
- Reduces the chance of losing requirements in a discussion.
- Provides a run record that can be checked later.
Setup
Build it in a few focused steps.
- 1Connect Notion and Google Analytics to Notis once in the portal.
- 2Create an automation in Automations or ask Notis to create it in conversation.
- 3Write one instruction asking Notis to request the expanded dataset when a comment clearly specifies one.
- 4Select the Notion Comment Created trigger and pick a channel for run reports.
- 5Test with a real comment describing a dataset need.
Questions about this workflow
Does this require comment access?
Yes. The Notion integration needs the Read comments capability, and may need reauthorization if that capability was enabled later.
Will every comment create a dataset?
Use the instruction to request a dataset only when the comment clearly describes that need, then review the run report.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Google Analytics. A trigger fires from one place; an action lands in another.
Notion triggers
Google Analytics actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Expanded Data Set
Tool to create an expanded data set for a property. use when you need to combine specific dimensions and metrics into a custom dataset after property creation.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Account
Tool to retrieve a single account by its resource name. use when you need detailed account info after confirming the account resource name (e.g., accounts/100).
All Page Events
Triggers when any Notion page is created or updated across the workspace.
List Accounts
Tool to list all accounts accessible by the caller. use when you need to enumerate all google analytics accounts your credentials can access.
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 Audiences
Tool to list all audiences on a property. use when you need to fetch all audiences for a ga4 property after confirming its existence.
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 Google Analytics, 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 Google Analytics.