Automatically audit Notion data quality nightly
Data quality issues in Notion go undetected and cascade downstream. Notis audits your Notion databases every night, checking for null fields, duplicates, and schema drift, logging issues to BigQuery for review.
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
Dirty data in Notion breaks dashboards and queries downstream. Without nightly audits, data quality degradation goes unnoticed until it causes real problems.
- Catch data quality issues before they break downstream queries
- Nightly reports let you fix issues first thing in the morning
- Automated checks without manual review or SQL writing
- Historical quality metrics to track improvement over time
Setup
Build it in a few focused steps.
- 1Connect Notion workspace to Notis.
- 2Connect Google BigQuery to Notis.
- 3Tell Notis: 'Every night at midnight, audit all Notion databases. Check for: empty fields, duplicate rows, schema mismatches, and rows with no creator info. Log any issues to a BigQuery data_quality_audit table.'
- 4Select 'Scheduled (cron)' as the trigger and set it to run nightly.
- 5Choose your reporting channel.
- 6After the first audit runs, build a dashboard to visualize data quality trends.
Questions about this workflow
Can I customize what counts as a data quality issue?
Yes. Define nullability rules, uniqueness constraints, allowed values, and any other quality checks specific to your databases.
What happens when an issue is found?
Notis logs it to BigQuery. You can also ask for alerts via Slack or email if issues exceed a threshold.
Can I run audits more frequently than nightly?
Yes. You can audit every 4 hours, daily, or any frequency. Nightly is common for cost.
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.