Skip to content
Notis

Pair new measurement data sources with Analytics datasets

When a measurement data source is added, have Notis carry its purpose into an expanded dataset request.

Trigger

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.

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

A new data source can signal a new measurement need, but the corresponding Analytics preparation may be missed.

  • Prompts Analytics preparation when a source is introduced.
  • Keeps measurement work aligned across tools.
  • Creates a visible run report for follow-up.

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 one.
  • 3Describe that a new measurement data source should prompt the expanded dataset request in its context.
  • 4Choose the Notion Data Source Created trigger and a channel for run reports.
  • 5Test with a real new data source and inspect the run outcome.

Questions about this workflow

Could a template cause multiple runs?

Yes. A template-based database can create multiple data sources and fire an event for each.

Does this create a Notion data source?

No. The trigger reacts to one being created; the action requests an Analytics dataset.

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.

TriggerScheduled

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.

ActionInstant

Webhook trigger

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

TriggerInstant

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).

ActionInstant

All Page Events

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

TriggerPolling

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.

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

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.

ActionInstant

New Comment

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

TriggerPolling

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

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 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.