Keep supplier research moving from the shortlist
Create a shortlist entry in Notion and have Notis show requests from its related Asin collection, so sourcing research can continue without a separate search.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
List Collection Requests
Tool to list all requests in a collection (paginated). use when you need to paginate through requests for a specific collection.
Why this helps
Supplier shortlist work often stalls while you locate the product request trail.
- See existing requests at the moment a shortlist entry is added.
- Keep sourcing research connected to its product context.
- Reduce repeated navigation during evaluation.
Setup
Build it in a few focused steps.
- 1Connect Notion and Asin data api to Notis once through the portal.
- 2Create an automation or tell Notis to list requests in the relevant sourcing collection when a shortlist entry is added.
- 3Select New Page for the shortlist data source.
- 4Choose the channel for run reports and test with one real shortlist page.
Questions about this workflow
Does this compare or approve suppliers?
No. It lists requests in the selected collection for manual review.
Can I reuse this for separate shortlists?
Create separate automations with clear instructions and the relevant Notion trigger scopes.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Asin data api. A trigger fires from one place; an action lands in another.
Notion triggers
Asin data api actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Clear multiple collection requests
Tool to delete multiple requests from a collection by ids. use when you need to remove a selected set of request entries from an existing collection in a single call.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List Collection Requests
Tool to list all requests in a collection (paginated). use when you need to paginate through requests for a specific collection.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
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 Asin data api, 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 Asin data api.