Keep model research aligned with design decisions
Update the decision in Notion and get Cults discovery based on the current direction.
Trigger
Page Content Updated
Triggers when the body content of a Notion page is 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 page content edit in the workspace the integration has access to. Notion aggregates content edits within a short window (~60s typical).
Action
Cults GraphQL POST
Tool to execute a GraphQL operation against the Cults API. Use when you need to fetch or mutate data via the Cults GraphQL endpoint.
Why this helps
Old marketplace research lingers after a design direction changes, creating avoidable rework.
- Refreshes discovery after meaningful page content changes.
- Reduces the chance of relying on model research tied to an outdated direction.
Setup
Build it in a few focused steps.
- 1Connect Notion and Cults to Notis once in the portal.
- 2Create an automation in Notis to search Cults when the design decision page content is updated.
- 3Write one instruction asking Notis to use the updated decision to find relevant models and summarize why they may fit.
- 4Choose the Notion Page Content Updated trigger scoped to the decision page and select a channel for run reports.
- 5Test by making one real decision update and reviewing the search.
Questions about this workflow
Will it search after every edit?
Notion aggregates content edits in a short window. The automation runs from the configured page content update trigger.
Can the search use constraints in the decision?
Yes. Include the constraints in your plain-language instruction and decision page.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Cults. A trigger fires from one place; an action lands in another.
Notion triggers
Cults actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Approved Origins
Tool to retrieve approved sharing origins from Cults. Use when you need to infer the allowed domains for the Share on Create action. Use after authenticating with Cults.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Cults GraphQL POST
Tool to execute a GraphQL operation against the Cults API. Use when you need to fetch or mutate data via the Cults GraphQL endpoint.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Share on Create (FR)
Tool to prefill a new creation on Cults (French locale). Use when you need to generate a one-click share link for a 3D file. Use after your site is approved by Cults.
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.
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 Cults, 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 Cults.