Notion Schema Changes Auto-Sync to Airtable Fields
Add a new field to a Notion database, and Notis instantly creates the matching field in Airtable. Your structure stays synchronized automatically.
Trigger
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.
Action
Create Field
Creates a new field within a specified table in an airtable base.
Why this helps
You add a new property to track in Notion but forget to add it to Airtable, or you do it weeks later. Then data is missing in one system, and you have to backfill manually.
- Schema stays synchronized without manual work
- New fields are available immediately in both tools
- Reduces backfill work and data inconsistency
- Fewer gaps in your tracking structure
Setup
Build it in a few focused steps.
- 1Connect Notion and Airtable to Notis
- 2Tell Notis: 'Whenever I add or change a field in my Notion database, create or update the matching field in Airtable'
- 3Specify which Notion database and Airtable table to watch
- 4Choose your notification channel
- 5Add a new field to your Notion database and watch Airtable create it automatically
Questions about this workflow
Are all field types supported (text, number, select, date, etc.)?
Most are. Notis maps common types from Notion to Airtable equivalents. Complex types may need manual adjustment; ask Notis about your specific use case.
What if I rename a field in Notion? Does Airtable update?
Yes, Notis detects renames and updates the Airtable field name to match, ensuring consistency.
Do existing records need to be migrated when a field is added?
No, the new field is added to the table structure. Existing records will have empty values for the new field unless Notis backfills with a default.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Airtable. A trigger fires from one place; an action lands in another.
Notion triggers
Airtable actions
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create base
Creates a new airtable base with specified tables and fields within a workspace; ensure field options are valid for their type.
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.
Create Comment
Creates a new comment on a specific record within an airtable base and table.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Create Field
Creates a new field within a specified table in an airtable base.
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.
Create multiple records
Creates multiple new records in a specified airtable table.
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.
Create a record
Creates a new record in a specified airtable table; field values must conform to the table's column types.
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.
Create table
Creates a new table within a specified existing airtable base, allowing definition of its name, description, and field structure.
New Page
Triggers when a new page is added to a Notion database.
Delete Comment
Deletes an existing comment from a specified record in an airtable table.
Page Added to Page
Fires when a new subpage (a `child_page` type block) is added under a specified parent Notion page.
Delete multiple records
Deletes up to 10 specified records from a table within an airtable base.
Connect any two apps with Notis in the middle.
Not just Notion and Airtable. Any combination from 985+ 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 Airtable.