Automatically audit Notion changes hourly to BigQuery
Compliance audits demand audit trails, but Notion's audit log is buried and hard to export. Notis runs hourly audits of workspace changes and logs them to BigQuery so you have a compliance-ready record.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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
Compliance requirements demand audit trails. Notion's built-in audit log is hard to access and export, creating compliance risk and slow audit responses.
- Compliance-ready audit trail logged continuously without manual export
- Query 'who changed what, when, and where' for any compliance question
- Automate audit report generation from BigQuery
- Reduce manual effort on compliance audits by 80%
Setup
Build it in a few focused steps.
- 1Connect Notion workspace to Notis.
- 2Connect Google BigQuery to Notis.
- 3Ask Notis: 'Every hour, export all Notion workspace changes from the past hour (pages created/updated, databases added, users active) to a BigQuery audit_log table with timestamps and user info.'
- 4Select 'Scheduled (cron)' as the trigger and set it to run hourly.
- 5Pick your reporting channel.
- 6After 24 hours of data, build a dashboard or query to verify the audit trail is complete.
Questions about this workflow
Can I adjust the frequency or just use hourly?
You can set any frequency: every 30 minutes, hourly, every 4 hours, etc. Hourly is common for compliance.
What data is included in the hourly audit?
Page creates/updates, database changes, user activity, timestamps, and editor info. You can customize what gets logged.
How far back can I query?
As far back as the audit logs exist in BigQuery. Once data is there, it's permanently queryable.
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.