Recheck CRM fields when your Notion schema changes
When you adjust a Notion data source, let Notis retrieve CRM field definitions so your process notes can stay aligned with the information CRM tracks.
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
List Folder Fields
Tool to list folder fields in NetHunt CRM. Returns the field definitions for a specific folder. Use when you need to retrieve all field metadata for a given folder ID.
Why this helps
A workflow reference can become outdated after a Notion schema change, creating uncertainty about what information to capture.
- Refresh the CRM field reference at a natural process review point.
- Make schema changes easier to account for in sales documentation.
- Reduce uncertainty about which information CRM currently tracks.
Setup
Build it in a few focused steps.
- 1Connect Notion and NetHunt CRM to Notis once in the portal.
- 2Create an automation in the portal or ask Notis to review CRM folder fields when a Notion schema changes.
- 3Write one instruction asking Notis to retrieve the relevant NetHunt folder's field definitions and explain any useful alignment points for the updated data source.
- 4Select the Notion Data Source Schema Updated trigger and choose a channel for run reports.
- 5Rename or add one real schema property and review the resulting field reference.
Questions about this workflow
Does this run for each existing row too?
The schema trigger is the structural-change signal. Notion may also send page property events when a column is added.
Can it edit either schema?
No. It retrieves CRM field definitions and reports them for review.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to NetHunt CRM. A trigger fires from one place; an action lands in another.
Notion triggers
NetHunt CRM actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete Record
Tool to delete a NetHunt CRM record by ID. Use when you need to permanently remove a record from the system.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Find Records
Tool to find records by ID or text query in NetHunt CRM. Search for records within a folder using record ID or search query. Use when you need to locate specific records in a folder.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get New Call Logs
Find recently created call logs in NetHunt CRM. Returns call logs created after a specified time. Use when you need to retrieve new call activity from a specific folder.
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.
Get New Comments
Tool to find recently created record comments in a NetHunt CRM folder. Returns comments created after a specified time (defaults to last 24 hours).
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get New Google Drive Files
Tool to find recently created Google Drive files linked to NetHunt CRM records. Use when you need to retrieve files created after a specific time in a NetHunt folder. Returns file metadata including Google Drive links, MIME types, and associated record IDs. Useful for tracking new document uploads and file attachments.
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.
Get New Records
Tool to find recently created records in NetHunt CRM. Use when you need to retrieve records that were created after a specific time in a given folder. Returns record details including ID, creation time, and field values. If no 'since' time is specified, returns records from the last 24 hours.
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.
Get Record Changes
Tool to find recent record changes in a NetHunt CRM folder. Returns change history including CREATE, UPDATE, DELETE actions with field-level diffs. Use when you need to track modifications to records, audit changes, or sync data based on recent updates.
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.
Get Updated Records
Tool to find recently updated records in NetHunt CRM. Returns records updated after a specified time, optionally filtered by field names. Use when you need to track changes or sync records that have been modified.
Connect any two apps with Notis in the middle.
Notion and NetHunt CRM, 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 NetHunt CRM.