Remove Vision catalog membership from a Notion update
Document an approved catalog removal in Notion and have Notis unlink the named Product from the named set.
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
Remove Product from ProductSet
Tool to remove a Product from a specified ProductSet. Use after creating both resources in the same project/location to unlink a product from its set.
Why this helps
Catalog membership cleanup can be forgotten after a decision is recorded in a task or product database.
- Turns an explicit record change into a focused cleanup action.
- Preserves the Product itself while removing its set membership.
- Makes the target resources traceable to a Notion request.
Setup
Build it in a few focused steps.
- 1Connect Notion and Google Cloud Vision to Notis once.
- 2Create the automation in the portal or ask Notis conversationally.
- 3Write one instruction to remove the identified Product from the identified ProductSet only when the updated Notion record clearly requests removal.
- 4Pick Page Properties Updated and select the run-report channel.
- 5Test with one approved removal and verify the Product remains while membership is removed.
Questions about this workflow
Does this delete the Product?
No. It removes the Product from the ProductSet and leaves the Product resource intact.
How should accidental removals be avoided?
Have the instruction require a clear removal request in the updated record and test with the exact intended resource names.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Google cloud vision. A trigger fires from one place; an action lands in another.
Notion triggers
Google cloud vision actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Vision Product
Tool to create and return a new Product resource. Use when you need to register a product in a specific project/location after preparing product details.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create ReferenceImage
Tool to create a ReferenceImage under a product. Use when adding a new image to a product for detection.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Delete Product
Tool to permanently delete a Product and its reference images. Use after confirming the product's resource name.
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 Product
Tool to get information associated with a Product. Use when you have the product resource name and need its details.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Product Set
Tool to get a ProductSet. Use when you need metadata details of an existing ProductSet by its full resource name. Use after obtaining the resource name.
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.
Import Product Sets
Tool to asynchronously import reference images into ProductSets from a CSV in GCS. Use when you need to bulk import images into product sets via a Cloud Storage CSV.
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.
List IndexEndpoints
Tool to list IndexEndpoints in a project and location. Use when you need to retrieve existing IndexEndpoints and handle pagination.
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.
List Locations
Tool to list available Vision AI service locations for a project. Use when you need to discover supported regions before making region-specific API calls.
Connect any two apps with Notis in the middle.
Notion and Google cloud vision, 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 Google cloud vision.