Keep contact context close during Notion database changes
When you revise how your team tracks people, have Notis bring a relevant Orbit profile into view for review.
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
Read Person Profile
Read the stored profile for one person: identity, contacts, history, sections, sources.
Why this helps
Changing a tracking system can distract from the relationship context that made its records useful.
- Review a person's stored context while updating your contact process.
- Avoid searching separately for a relevant profile during maintenance.
- Keep relationship history in view alongside structural changes.
Setup
Build it in a few focused steps.
- 1Connect Notion and Orbit to Notis once through the portal.
- 2Create the automation in the portal or ask Notis conversationally.
- 3Use one instruction that identifies the relevant person and asks Orbit to read their stored profile when the contact data source schema changes.
- 4Select the Notion Data Source Schema Updated trigger for the contact source and choose a report channel.
- 5Test with a planned schema change and a clearly identified person.
Questions about this workflow
Will this read every contact profile after a column change?
The action reads one person's stored profile. State the intended person in the instruction and use this workflow for a relevant review case.
What does the trigger report?
The event is a data source schema update, such as adding, removing, or renaming a column.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Orbit. A trigger fires from one place; an action lands in another.
Notion triggers
Orbit actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Find People
Find people from a description, criteria or identity signals, with source-backed context.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Read Person Profile
Read the stored profile for one person: identity, contacts, history, sections, sources.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Batch Enrich Profiles
Build up to 20 people's profiles to partial or full depth in one call.
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.
Enrich Person Profile
Build one person's profile to partial or full depth from live web and public sources.
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.
Connect any two apps with Notis in the middle.
Notion and Orbit, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Orbit.