Ground each marketplace idea in existing requests
Capture an idea in Notion and let Notis list the requests in your chosen Asin collection, so the next research step starts with what is already queued.
Trigger
Page Created
Triggers when a new Notion page is created. Customer optionally scopes with at most one of: - data_source_id: new row in this data source - parent_page_id: new sub-page under this page (immediate parent only) With neither set, fires for any new page in the workspace the integration has access to. Notion sends ~60s aggregation latency on most events.
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
New ideas can lead to duplicate research when existing requests are hard to see.
- Check existing collection entries before starting another investigation.
- Make idea capture more actionable.
- Keep research kickoff lightweight.
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 chosen idea-research collection when a marketplace idea page is created.
- 3Select Page Created and scope it to the relevant parent page or data source if useful.
- 4Choose a run-report channel and test with one real idea page.
Questions about this workflow
Does this judge whether an idea is viable?
No. It lists existing requests to help you choose a next research step.
Can I use it for a particular idea area?
Use the trigger scope and plain-language instruction to identify the intended Notion area and Asin collection.
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.