Restart prospect research from the details you just updated
Change a prospect record in Notion and have Crustdata help surface decision-maker context for the next step.
Trigger
Page Properties Updated
Triggers when properties of a Notion page are updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.
Action
Filter decision makers data
Filters and retrieves decision maker data from the crustdata b2b saas integration platform based on complex criteria. this endpoint allows for advanced querying of decision maker information using a combination of filters, pagination, sorting, and title-based filtering. it's designed for scenarios where specific subsets of decision maker data need to be extracted or analyzed. the endpoint supports nested logical conditions in filters, enabling highly targeted data retrieval. use this when you need to perform detailed analysis or reporting on decision makers across various organizations or industries. note that the endpoint requires careful structuring of the request body to effectively utilize its advanced filtering capabilities.
Why this helps
A change in account focus can leave old prospect research scattered or out of date.
- Connect updated account context to a relevant decision-maker search.
- Avoid reopening several tabs to remember where prospect research stopped.
- Make the next research step easier to pick up.
Setup
Build it in a few focused steps.
- 1Connect Notion and Crustdata to Notis once in the portal.
- 2Ask Notis for an automation that uses changed prospect details to find relevant decision makers in Crustdata and summarize results.
- 3Choose the Notion Page Properties Updated trigger for the prospect database and select a report channel.
- 4Test by updating one real prospect record.
Questions about this workflow
Can the search focus on particular roles?
Yes. Include the role or title criteria in the plain-language instruction to Notis.
Will every property change cause a search?
The selected Notion trigger can fire on property updates. State in the instruction when the search is useful and what changes should prompt a report.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Crustdata. A trigger fires from one place; an action lands in another.
Notion triggers
Crustdata actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Enrich person screener
The screener person enrich endpoint enriches person data by providing additional information based on the given query. it allows users to retrieve detailed information about individuals, which can be useful for various purposes such as customer profiling, lead generation, or data verification. this endpoint should be used when you need to augment existing person data with additional details or verify information about a specific individual. the enrichment process draws from crustdata's extensive database and real-time data sources to provide up-to-date and comprehensive information. users can customize the response by specifying the exact fields they need, optimizing data transfer and processing. note that the availability and accuracy of enriched data may vary depending on the input provided and the information available in crustdata's systems.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Fetch headcount by facet timeseries
Retrieves headcount data as a timeseries with faceted analysis capabilities. this endpoint allows users to fetch detailed headcount information over time, applying complex filters, pagination, and sorting. it's particularly useful for hr analytics, workforce planning, and organizational growth analysis. the endpoint supports nested logical operations in its filtering mechanism, enabling highly specific queries. users can paginate through large datasets and sort results based on multiple criteria. while powerful, this endpoint requires careful construction of the filters parameter to ensure accurate data retrieval. it should be used when detailed, time-based headcount analysis is needed, but may not be suitable for simple, non-time-series headcount queries or for real-time data needs due to its complexity.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Fetch investor portfolio data
Retrieves comprehensive investor portfolio data from the data lab section of the crustdata api. this endpoint provides access to detailed information about investor portfolios, including investment holdings, performance metrics, and other relevant data points. it is designed to support investment analysis, portfolio management, and decision-making processes in a b2b context. the endpoint should be used when detailed investor portfolio information is required for tasks such as investment screening, performance tracking, or generating analytical reports. it's important to note that this endpoint may not provide real-time data and the frequency of updates should be verified in the api documentation. additionally, users should be aware of any data privacy and usage restrictions that may apply to the retrieved investor information.
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.
Filter decision makers data
Filters and retrieves decision maker data from the crustdata b2b saas integration platform based on complex criteria. this endpoint allows for advanced querying of decision maker information using a combination of filters, pagination, sorting, and title-based filtering. it's designed for scenarios where specific subsets of decision maker data need to be extracted or analyzed. the endpoint supports nested logical conditions in filters, enabling highly targeted data retrieval. use this when you need to perform detailed analysis or reporting on decision makers across various organizations or industries. note that the endpoint requires careful structuring of the request body to effectively utilize its advanced filtering capabilities.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Post funding milestone timeseries data
The fundingmilestonetimeseries endpoint retrieves time-series data related to funding milestones for companies. it allows for complex querying of funding events over time, with flexible filtering, pagination, and sorting options. this endpoint is particularly useful for analyzing funding trends, comparing company funding histories, or tracking specific funding events across multiple organizations. the data returned is based on the specified filters and can be tailored to focus on particular time ranges, funding stages, or company characteristics. while it provides comprehensive funding milestone data, it does not include detailed company information beyond what's directly related to funding events.
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.
Post headcount timeseries data
Retrieves filtered and sorted headcount timeseries data from the crustdata data lab. this endpoint allows for complex querying of historical headcount information, enabling users to analyze workforce trends over time. it supports advanced filtering with nested conditions, pagination for handling large datasets, and customizable sorting. ideal for generating reports, conducting workforce analysis, or integrating headcount data into third-party business intelligence tools. note that the specifics of the returned data structure are not provided in the given schema.
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.
Post job listings table data
This endpoint retrieves filtered and sorted job listings data for specified company tickers from a chosen dataset in the crustdata platform. it allows for highly customizable queries with complex filtering conditions, pagination, and sorting options. the endpoint is designed for bulk data retrieval and analysis of job market trends across multiple companies. use this endpoint when you need to fetch and analyze job listing data for specific companies, apply custom filters to narrow down the results, or when you want to paginate through large sets of job data. it's particularly useful for market research, competitive analysis, or tracking employment trends in specific industries or companies. note that this endpoint requires careful construction of the request body, especially for the filters parameter, which can support nested logical conditions. the performance and response time may vary depending on the complexity of the filters and the amount of data requested.
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.
Post web traffic data
Retrieves filtered and sorted web traffic data from the crustdata platform. this endpoint allows for complex querying of web traffic information using nested conditions and logical operators. it supports pagination for handling large datasets and provides sorting capabilities for customized data presentation. use this endpoint when you need to analyze web traffic patterns, filter data based on specific criteria, or extract insights from your web analytics. the endpoint is particularly useful for generating reports, identifying trends, or monitoring key performance indicators related to web traffic.
Connect any two apps with Notis in the middle.
Notion and Crustdata, 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 Crustdata.