Automatically log all Notion workspace changes to BigQuery
Workspace chaos means changes happen everywhere and nowhere simultaneously. Notis logs every page creation and update to one BigQuery table so you always know what's changing and by whom.
Trigger
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Action
Query
Query tool will run a sql query in bigquery. note: make sure the query being input in a single line format. for example, select * from sample dataset.sample table where column name = 'value'
Why this helps
Changes scatter across your Notion workspace without a central audit trail. You can't answer 'what changed today?' without opening Notion and manually reviewing pages.
- Single place to audit all workspace changes without opening Notion
- Compliance-ready audit log with timestamps and user info
- Query 'what changed and when' across your entire workspace
- Detect unusual activity patterns or over-edits
Setup
Build it in a few focused steps.
- 1Connect Notion workspace to Notis.
- 2Connect Google BigQuery to Notis.
- 3Ask Notis: 'When any Notion page is created or updated, log the page ID, title, event type (create/update), timestamp, and creator/editor email to BigQuery.'
- 4Select 'All Page Events' as the trigger.
- 5Pick your reporting channel.
- 6Test by creating or updating a page in Notion and confirming the record appears in BigQuery.
Questions about this workflow
Will this log every keystroke or just page saves?
Notion batches edits within a ~60-second window, so you get a single entry per editing session, not per keystroke.
Can I exclude certain pages or databases?
Yes. Notis can filter to log only pages from specific databases, teamspaces, or parent pages.
How far back does the audit trail go?
Notion's events are continuous, so Notis captures all future events. For historical data, you'd need to seed BigQuery separately.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Google BigQuery. A trigger fires from one place; an action lands in another.
Notion triggers
Google BigQuery actions
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Query
Query tool will run a sql query in bigquery. note: make sure the query being input in a single line format. for example, select * from sample dataset.sample table where column name = 'value'
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.
New Page
Triggers when a new page is added to a Notion database.
Page Added to Page
Fires when a new subpage (a `child_page` type block) is added under a specified parent Notion page.
Connect any two apps with Notis in the middle.
Not just Notion and Google BigQuery. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Google BigQuery.