Review search guidance when your Notion schema changes
When you add, remove, or rename properties in a Notion data source, fetch Clay's query reference to make it easier to revisit search instructions affected by the change.
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
Get Search Query Reference
Fetch the query-language reference for authoring advanced people/company searches.
Why this helps
A structural change can quietly make an established search routine harder to understand or maintain.
- Get Clay's query-language reference when data structure changes.
- Create a timely cue to review search practices.
- Reduce the mental load of remembering how advanced queries are authored.
Setup
Build it in a few focused steps.
- 1Connect Notion and Clay to Notis once through the portal.
- 2Tell Notis to fetch Clay's advanced search query reference when a chosen Notion data source schema changes.
- 3Choose Data Source Schema Updated, scoped to the data source if useful, and select a report channel.
- 4Test with a real schema update and confirm the reference is fetched.
Questions about this workflow
What kinds of schema changes trigger it?
The event covers column add, remove, or rename operations and includes updated property details.
Does it create or run a search?
No. It fetches the query-language reference for authoring advanced people or company searches.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Clay. A trigger fires from one place; an action lands in another.
Notion triggers
Clay actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Find Mobile Phone
Find a person's mobile phone number from their LinkedIn URL, name, and company.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Company Employee Count
Get a company's current employee headcount from its domain.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Advanced Search
Start an advanced-query search for people or companies and get a search_id.
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.
Find Company Domain from Name
Resolve a company name to its primary website domain.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Search Query Reference
Fetch the query-language reference for authoring advanced people/company searches.
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.
Fetch Advanced Search Results
Fetch the next page of results for an advanced search by search_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 Clay, 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 Clay.