Check available audiences as campaign plans start
Start a campaign page with a quick inventory of the audiences already available in Analytics.
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
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.
Why this helps
Campaign planning can gather momentum before anyone checks whether the expected audience exists.
- Adds an audience readiness step at campaign kickoff.
- Helps spot a missing audience earlier in planning.
- Keeps the check accessible from Notis run reports.
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 conversationally.
- 3Describe that a new campaign page should prompt a list of available Analytics audiences.
- 4Choose the Notion Page Created trigger and select the campaign page context.
- 5Choose a run-report channel and test with one real campaign page.
Questions about this workflow
Can it confirm that an audience is ready to use?
It lists audiences on the property; the list alone does not confirm campaign eligibility or performance.
Does it create a missing audience?
No. The listed action retrieves the existing audience list.
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.