Keep Hubspot Properties Aligned With Notion Schema Changes
Modify your Notion database schema and Hubspot properties update automatically. Your CRM structure evolves with your data model without manual property creation.
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
Archive batch of properties
Archives a batch of properties by their internal names for a specified hubspot crm object type; this operation is idempotent and safe to retry.
Why this helps
You add a new column to your Notion database but forget to create the corresponding property in Hubspot. Your CRM and Notion schemas drift apart, causing confusion and data mismatch.
- Schema stays in sync across tools
- Automatic property creation without manual steps
- Never miss a new field in your CRM
- Reduce cognitive load of maintaining structure
- Scale your properties with your data needs
Setup
Build it in a few focused steps.
- 1Connect Notion and Hubspot to Notis
- 2Create the automation: 'When Notion database columns are added or renamed, create or update Hubspot properties'
- 3Specify which Notion databases to monitor for schema changes
- 4Set column-to-property mapping rules (or let Notis auto-map by name)
- 5Test by adding a new column to a Notion database and verify the property appears in Hubspot
Questions about this workflow
Does this handle column deletions?
By default, deleted Notion columns don't auto-delete Hubspot properties (to be safe). You can configure it differently if you prefer automatic cleanup.
What about Notion property types like checkboxes or dates?
Notis maps Notion types to the closest Hubspot equivalent (e.g., checkbox becomes boolean property, date becomes date property).
Can I rename properties to match a convention?
Yes. Tell Notis your naming convention (e.g., 'convert spaces to underscores') and it will apply it when creating properties.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Hubspot. A trigger fires from one place; an action lands in another.
Notion triggers
Hubspot actions
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Add asset association
Associates an existing asset ('form', 'object list', or 'external web url') with a specified hubspot marketing campaign.
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.
Add token to event template
Adds a new custom data token to an existing event template for a specified hubspot application, optionally populating a crm object property if objectpropertyname is provided.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Archive email
Archives the hubspot email specified by `emailid` by moving it to the recycling bin, making it inaccessible unless restored.
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.
Archive a batch of emails by ID
Archives multiple hubspot crm emails by id; ids must exist as archiving is irreversible.
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.
Archive a batch of quotes by id
Archives a batch of existing, non-archived quotes by their ids; this action is irreversible and useful for managing outdated or irrelevant quotes.
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.
Archive batch of companies by id
Archives a batch of companies by their unique ids; targeted companies must exist, not be previously archived, and this api operation is irreversible.
New Page
Triggers when a new page is added to a Notion database.
Archive batch of contacts by id
Archives a batch of existing contacts by their hubspot crm ids, rendering them inactive; this action is irreversible via the api and requires manual restoration or a separate unarchive endpoint.
Page Added to Page
Fires when a new subpage (a `child_page` type block) is added under a specified parent Notion page.
Archive batch of deals by id
Archives a batch of existing deals by their unique hubspot ids, removing them from active views and reports (soft delete); archived deals may be restorable.
Connect any two apps with Notis in the middle.
Not just Notion and Hubspot. 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 Hubspot.